[ros-general] 0x3ED error in ReactOS explorer

[Karim Liman-Tinguiri]

Hi,
 Here's a curious (and very easy to reproduce) error in ReactOS explorer.
After downloading qemu preloaded with ReactOS and running it, going to
ReactOS explorer shows two hard drive: C and D while qemu has only one
mounted (I can see a c.img but no d.img in qemu's folder). Clicking on D
produces a "*0x3ed unknown error*" (I have attached a screenshot).
 I guess this issue has two solutions:
- Either, the problem comes from qemu reporting an nonexistant hard drive,
in which case, the 0x3ED exception should be intercepted and be displayed
instead as: "Unable to access D drive".
- Or qemu's indeed not reporting the D drive in which case the bug comes
from the ReactOS kernel or ReactOS explorer.
 I could have implemented the corrections in the sources myself and sent
them here already, but I haven't done so since (1) I wasn't sure whether the
issue came from qemu reporting nonexistent hard drives to the ReactOS
kernel, from the kernel reporting nonexistent hard drives to ReactOS
explorer or from the ReactOS explorer reporting an nonexistent hard drive to
the user. (2) I didn't know where the error strings are located in the
source files (it would be great if somebody pointed me to the string table
for ReactOS explorer) and, even after a lookup on Internet, couldn't find
the exact string corresponding to the 0x3ED error code.
 - Warz Cannon.