IDE controller resource conflict cause blue screen after reboot

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi im new in the world of xp embedded systems, and I have try to build a test
system by adding
Shell Application Compatibility from category (all setting ticks)
Software : Test & Development; Software : System : User Interface :
Infrastructure;
(all settings have been marked/ticked/, italics after running dependenccy
check)

and

WinLogon Sample Macro from category
Software : Test & Development;
(all settings except
Standard IDE/ESDI Hard Disk Controller,
Secondary IDE Channel,
have been marked/ticked/ ,italics after running dependenccy check)

After FBA have runs sucessfullly and the target(2nd partition/ dual boot)
boot into the system)
I immediate go to the device manager from the System Control Panel.

There i see 2 Standard IDE/ESDI Hard Disk Controller
and one unknown IDE contoller in the IDE ATA/ATAPI Controller catagory.
I update the unknown IDE contoller driver from my first
patition(C:\windows\system32\drivers\)
and was sucessful and two addition contoller appear primary ide channel and
secondary ide channel.
______________________________________________________________
Here the problem, the two new contollers have resources conflictwith the 2
Standard IDE/ESDI Hard Disk Controller and if i restart the computer and
reboot
blue screen of death appear. Any idea how to resolve this issue when all
possible IRQ are " seen by the computer " to be used up.
 
The best way to make an image for a particular piece of hardware is to
install XPPro on your target hardware, run the tap.exe tool on it to
generate a devices.pmq file, import it into target designer and resolve
dependencies. I've never gone near the sample macro.
 
Adora,
The best way
Click to expand...

The quickest way, but not the best :-)
At some point you'd want to optimize your image footprint and that is where you realize that TAP/XPP approach is really time
consuming.

At least start with TAP on WINPE if possible.
 
KM said:
Adora,




The quickest way, but not the best :-)
At some point you'd want to optimize your image footprint and that is where you realize that TAP/XPP approach is really time
consuming.

At least start with TAP on WINPE if possible.
Click to expand...
Probably the best for someone just starting out, though, as installing
XPPro gives you a good idea if all your drivers are going to work. I
often keep a disk with XPPro for my hardware around so I can check
whether issues I'm having on my XPe image also happen under Pro. Makes
it easier to troubleshoot...
 
Back
Top