Jump to content

uOpt

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by uOpt

  1. I can confirm that just going back to RC8 and doing the same thing that failed in the release fixed the problem. Where do we report this problem, is there a bugzilla somewhere?
  2. I did some more sniffing and I believe my problem might be signed drivers. Maybe the above can be explained by the XP installer willing to pick the most suitable driver regardless of signing but the installed XP picks what looks like the most suitable driver that is signed? That would explain it if the XP CD had a signed driver for the ICH7 (desktop) but none for the ICH7M. I'll try RC8 and also the vitaligraf.de integrator.
  3. Hi, I'm having trouble getting XP Pro to install on a SATA ICH7M notebook. I have read all the SATA threads on this forum back to March, but my case seems to be unusual because the install works and it fails later. Short story: What happens for me is that the installation succeeds but that after the installation when XP starts on its own from the harddrive it doesn't have the disk controller driver and bluescreens. Or in other words: it is picking up the driver I integrated during the installation and it installs fine (which means it finds the harddrive), and only when it is supposed to reboot from the harddrive it fails. It does work when I move the such installed harddrive to my desktop board with Intel ICH7 (desktop variant) - which puzzles me even more. Long story: My girlfriend has a Fujitsu N3530 Notebook that comes with XP media. She needs XP Pro for her ASP work. Installing her full XP version after erasing the XP Media installation doesn't work because the notebook uses a SATA drive. Disk controller is Intel ICH7M (note "M"). We tried the F6 blues with a USB memory stick but XP wanted the driver twice, first it found it but on the second time it didn't. Bummer. So we go Nlite. We integrate the ICH7 driver into Nlite. There is only one *.sys file from Intel which is for all ICH7 variants, desktop and mobile. This NLite install CD installs fine. But when the finished XP installation wants to boot from harddrive it gives a bluescreen, with that hex code indicating it doesn't find the harddrive. (It took me a long time to get the hex key because it doesn't wait in the bluescreen, it's 1/10th of a second and then reboots, so that I spent an hour trying to make a camera shot of the bluescreen). OK, so it used my NLited driver during the installation, but not after the installation. But here's the kick: if I rip the harddrive out of the notebook and connect it to my desktop which has ICH7 (desktop variant), then it works just fine. That puzzles me no end, because how in the world did it end up picking the desktop driver over the ICH7M driver? Duh. Things I tried: I tried applying all Windoze updates while connected to my desktop. No change, moving it back to the notebook gives the bluescreen. in NLite we tried selecting only the ICH7M driver, so that the desktop driver woudln't be in. But that doesn't change anything. It is just one .sys file and the result is the same - installed XP boots only on the machine you did not install on. I have downloaded and installed the SATA drivers from the Fujitsu notebook website instead of Intel's site. They are the same as the Intel drivers I used, I did a binary comparision. So... I am out of ideas and looking for suggestions. How and why in the world does it end up using a different driver for the installed XP than it used for installing it? Thanks a lot in advance. Please help a poor guy who told her to get the Fujitsu and it would be no problem to install her XP.
×
×
  • Create New...