Jump to content

Kramy

Member
  • Posts

    153
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About Kramy

Kramy's Achievements

0

Reputation

  1. Perhaps - or perhaps it's exactly as I'm supposing it is - leftover drivers. I have a feeling if I do a fresh install on the unworking drive, it'll work fine. Of course, then all his info is gone, unless I back it all up first.
  2. Are you saying if you plug in a spare drive to the same IDE cable it works fine? Yep. Exact same cable, mobo port, and slave DVD drive. I know doing a fresh install will work fine, but if there's a way to get into safe mode, I can avoid doing that...
  3. I had some trouble figuring out the BSOD error code, because it reboots so fast, but yes, it appears to be a 0x0000007b. Unfortunately, your suggestion doesn't help. First, the HDD is a PATA drive, and the CD has been slipstreamed to SP3. Windows installs absolutely fine on a secondary drive I had lying around, so the problem must be related to old drivers that aren't being purged. If anyone has any suggestions on how to kick it out of wanting to install windows, so I can get into safemode, please post.
  4. Someone I know brought me a computer to fix. His old mobo died, so he got a newer one and new CPU. I had told him to "just do an XP repair install and install drivers off the CD when you're done". He followed the first part to the letter, but never got to the second. Unfortunately, the repair install doesn't seem to have disabled all the old mobo drivers, so it BSOD's immediately upon trying to enter Windows to resume setup. I tried to enter safe mode, but safe mode simply informs me that Setup cannot resume while in safe mode, and then reboots. How do I get into safe mode to purge the bad drivers, and complete the repair install? I have multiple other computers available, as well as a drive enclosure, so if it involves mucking around, simply provide instructions. Thanks. Oh, and he'd prefer not to have to reinstall everything - although if clearing it off is the only option, I suppose he'll have to. I just hope it isn't, since I'm sort of responsible for this mess.
  5. Realtek HD Audio for onboard 7.1 setups requires hhctrl.ocx, to access it in the control panel. Without access to this panel, there is no way to enable 'Stereo Mix', which lets you record what you hear. Major problem for screen recording software like FRAPS, but easily fixed by copying the file over to your system32 dir, or adding it to keepfiles in nLite.
  6. You're selecting components for removal. If you want to keep languages, start over, and don't select them.
  7. Isn't Dell like Acer - they ship modified CDs that restore the contents of the HD, rather than providing a disk that can do fresh installs? I use ImgBurn for all my ISO burning. Both Nero and nLite's burning give me disks with file copy errors, or problems booting.
  8. 1) It worked fine without 'CPU Intel' on my single-core Athlon XP. 2) 3) nLite 1.x RC Preset: TimeZone = (GMT-08:00) Pacific Time (US & Canada); Tijuana nLite 1.3 RC2 Preset: TimeZone = (GMT-08:00) Pacific Time (US & Canada); Tijuana nLite 1.3 RC2 Dialog: (GMT-08:00) Pacific Time (US & Canada); Tijuana They appear identical to me.
  9. Well, a while back I decided to finally upgrade my system, since my old one didn't cut it any more. I picked up a cheap X2 3800+, and a cheap mobo(which fried), so now I have a DFI Lanparty 590. For some reason my X2 shows up with 1 core in the task manager, and CPU-Z. It shows up with two in the device manager, but did not at first. Neither CPU was displayed until I stopped removing 'CPU Intel'. (I'm curious why an AMD CPU needs that component?) I can use -A0 and -A1 on shortcuts to direct programs to whichever core I desire, but programs don't actually pick up that there are two cores. Most curious. So anyone have a clue why nLite is doing this? 'Hardware Support\Multi-Processor Support' was left untouched. 2) Something I also stumbled across - the Windows CE USB Host is used for Firewire and USB on this board. It'd be nice if nLite mentioned that this component can be used for such purposes. 'May be linked to Firewire and USB support on enthusiast motherboards.' Beats having no description at all. 3) nLite keeps forgetting to load my timezone from a preset(GMT -8:00). Unless I set it in the unattended settings every single time before processing, it prompts me when installing windows. Cheers!
  10. Maybe something like GeoShell would interest you. You have to design your own UI, yes, but it's faster than using the Gecko engine.
  11. Kramy

    Stop Error!

    Err...I'm not the same person as above. I resolved my issue by using brute force...that is, I tried to eliminate every single possibility. Flipped floppy disks, floppy drives, used alternate IDE/floppy cables, flipped DVD-RW to CD-ROM, and disconnected all non-essential devices. Nomatter which floppy drive I used, just reading off the floppies would corrupt them; the next time a RAID driver was copied off, it would be filled with garbage and useless. I had to use several floppies and trade them out between file reads. The only reason I can come up with for that happening is some obscure motherboard problem that I've never encountered before... Now that Windows is actually up and running though, the system seems to be performing quite well, at least in benchmarks. Just pray I never have to set up another RAID array on that motherboard again!
  12. When integrating into Windows XP Home, the error message comes up. For Windows XP Pro and Windows 2000, there is no error message on my system, but it still blue-screens midway through installation. The partition screen looks really awful; my RAID array is listed, but so are all the single drives, and if I press the down key enough it BSODs. I have gotten Windows to finally install on this system, but something in nLite could possibly be improved.
  13. Not sure why, but seems unattended CDs don't like my Biostar TForce 550. Good thing to know if anyone plans on getting an AM2 system. I resolved all blue screens by attended-installing Windows 9 times. The first 8 times it had BSODs at various parts, all without a filename listed. The last time it made it through. -I copied to RAID drivers to several different floppies and flipped floppies every time it wanted the files. After files were read off a floppy, the disk would be useless and require a format. -Half way through the 9 attempts, I flipped floppy drives and got some new floppy disks, to make sure that wasn't the issue. Between the BIOS issues, RAM issues, IDE port issues, floppy disk issues, and driver issues...this mobo certainly has kept me busy! On the bright side, now that I finally have it working, HD Tach has informed me that my 4 drives in RAID-0+1 have a burst speed of over 360MB/sec! Awesome way to end the day!
  14. Kramy

    Stop Error!

    I get the problem 100% of the time, except when booting into safe mode. The error codes from the BSOD are as follows; for me, there was also no file listed: 0x0000007E (0xc0000005, 0xBAD88174, 0xF78DDD44, 0xF78DDA40) 0x0000007E (0xc0000005, 0xBAC0B174, 0xF78DDD44, 0xF78DDA40) - After disabling tons of services. No eventvwr errors, and no problems with devices in the device manager. All BIOS options configured optimally(USB legacy keyboard support OFF, all BIOS shadowing off, caching off, etc.) I have tried using nLite to integrate drivers, and just integrating a RAID driver with a floppy. Both methods fail, so I have to assume the problem is with a Windows driver, and not one of the ones I am using. I'm going to enable memory dumps, and after that try installing to a single drive. If I still get the BSOD, then something in Windows is screwed on my system. FYI, I have a Biostar TForce 550, Athlon X2 3800+, and 4 Seagate 320GB drives in RAID.
×
×
  • Create New...