This sounds like a load order problem, although I've never seen this result (not mounting of 2nd partition). Drivers without an "Order" specified load in reverse order when a hive is loaded. So, first boot driver A, B, C, D would load in that order. Then when the hive is restored and used driver D, C, B, A would load in that order. Take a good look at the debug output and the order of relevant
Firstly, sorry the code is poorly designed, but works! I cut and paste from some code I have. Call EnumSerialPorts() and return it into an AnsiString. The return value is a csv list of the COM ports that exists. NOTE: This code does not say if it is in use. If you call code to open a comport and it cannot be opened then either it is in use or it does not exists. //---------------------
Since you're talking about serial port and IRQ3 I suppose you're working on an x86 platform: -First of all you have to verify that your serial ports can actually use and share IRQ3: the BIOS documentation or, better, the hardware designer can help you. -OALIntrStaticTranslate will not work: this function does basically the following assignments: g_oalSysIntr2Irq[sysIntr] = irq
Luca, Thank you for your reply. Since reporting this, I have had some success by selecting different interrupts. As I recall now, this was a sensitive issue with the 4.2 version as well. Even though the interrupts are not designated according to the documemtation, they may still create conflicts. I wish this could be explained as to why? I actually have two other "embedded" plug-in serial
I have a PC-104 RF transceiver plug-in module that requires a normal serial port configuration in order to communicate. I had been using the following serial port setup in my platform.reg for CE4.2: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5] "SysIntr"=dword:1e "IoBase"=dword:0300 "IoLen"=dword:8 "DeviceArrayIndex"=dword:4 "Prefix"="COM" "Dll"="Com16550.Dll" "Order"
