Jump to content

big_sid

Member
  • Posts

    9
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About big_sid

big_sid's Achievements

0

Reputation

  1. Lucky me, I found a CD-RW... OK, I've created a bunch of nLite'd images now... 1 . XP (No ServicePack) + nForce SATARAID - Works OK 2 . XP + SP3 Slipstreamed + nForce SATARAID - Works OK 3 . XP + SP3 Slipstreamed + nForce SATARAID + nForce Network + Unattended Setup - Works OK So, I'm getting bored of this now, but I have to assume it was one of the hotfixes I'd added to the nLite image, but i haven't got the time to prove it at the moment. Thanks for the help though - Sid
  2. Sorry, lets take a step back because I think I'm confusing you... What I'm trying to get at is that I know the original XP CD-ROM source to be OK. I was able to perform an installation of XP Pro using the original XP Pro CD as it is and the nforce SATARAID drivers copied to two separate floppy disks and using the F6 method at the beginning of setup. The nLite'd CD I'm trying now is using the source from the known working XP CD and has the nForce SATARAID drivers slipstreamed (by selecting Multi-Drive Folder and TextMode as suggested earlier). But the nLite'd CD I'm using also has SP3 slipstreamed into it along with a handful of hotfixes, the, IE7 and the nForce Ethernet drivers. The original nLite'd CD had all this plus was configured for a fully automated (unattended) setup. This didn't work however, and I get that "Not enough virtual memory or paging file quote to process the specified command" flash up before the system reboots itself at the very start of the GUI installation of XP. So, I made another nLite'd CD only this time took out the entire unattended section, but kept the slipstreamed SP3, nForce drivers and hotfixes (including IE7) but this CD too has the same problem (error at first part of GUI setup followed by automatic reboot of system). I've removed 1GB of RAM (so i'm now down to 1GB from 2GB) and tried the last nLite'd CD again, but still the same problem. Unless anyone can suggest the cause of this I'm going to have to go through a process of elimination. I plan to start off with the original XP CD's source and slipstream the nForce SATARAID driver, but nothing else. If that works, I will repeat the process this time adding SP3, and so on adding in all the components until I find the one causing the problem... I just hope I have enough blank CD-Rs :-)
  3. I'm beginning to think this could be something to do with slipstreaming the SP3 stuff in. It's still doing the same.
  4. Already done that, that's how i figured out the 2 disk sataraid driver issue, using the original XP CD (no SP at all) and floppies and F6 to install the system. That worked OK, although like I originally said, half way through the install it started asking for nvRAID disk 2.
  5. 2 gig... i know 4 gig can cause problems with 32-bit XP... but I would have thought 2 gig should be OK. I did incorporate a lot of other bits into the nLite'd image (hotfixes and nvidia PnP network drivers) and made it unattended. I'm trying another image, this time not unattended.
  6. OK, I did as suggested with the nForce sataraid drivers, BUT now when the first stage of the GUI installer starts to boot, i'm getting the message "Not enough virtual memory or paging quota available to complete the specified operation." pop up in an error dialogue box then the system reboots, and goes into a loop doing this. Any ideas? Thanks - Sid
  7. Thanks Kelsenellenelvian & Fernando... I will give this a go later on, and try re-installing XP with the SATARAID drivers and slipstreamed SP3, and will let everyone know how I get on. Cheers - Sid
  8. Thanks for the reply. You're right, the nvrd32.inf file does indeed list all files which can be found under disk1 and disk2 folders under the [sourceDisksFiles.x86] section. It also seems to make reference to a second disk though like this... %NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk________ %NVRAID_DESC%=nvraid,SCSI\__NVIDIA_______Raid_Disk %NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk_20_____ %NVRAID_DESC%=nvraid,SCSI\__NVIDIA____Raid_Disk_20 Also, the file txtsetup.oem also includes reference of the two disks... [Disks] d1 = "NVIDIA RAID DRIVER (SCSI) disk 1",\disk1,\ d2 = "NVIDIA RAID DRIVER (SCSI) disk 2",\disk2,\ So would these files have to be modified to stop the driver thinking it needs to access a second disk, OR should I just use the .inf file from the folder from the extracted driver .exe which is IDE\WinXP\SATARAID which contains the contents of all of the floppy\disk1 and floppy\disk2 directories in nLite instead? *Files attached too - had to rename txtsetup.oem to txtsetup_oem.txt so it would upload. Many Thanks - Sid nvrd32.inf txtsetup_oem.txt
  9. Hi all, I spent all weekend trying to get an nLited Windows XP installation with nForce SATA/RAID drivers to work, but haven't been having much luck. I tested the general principle of the process (e.g. slipstreaming SP3 into XP Pro 32-bit, along with one textmode driver) to create a bootable ISO and used it to build a Windows XP Virtual Machine. This worked OK, so I decided to continue and try to rebuild my real PC using this method. After a lot of failed attempts (constant BSOD, reboot loop at the first boot after GUI install of XP completes), I think I know what the problem is, although I don't know how to resolve it. The latest WHQL nForce chipset drivers for my nForce 680SLi chipset (Asus Striker Extreme motherboard) contains SATARAID drivers, which if copied to floppy disk for a normal attended F6 style install require two (2) floppy disks to be inserted. I managed to get the OS installed, after ripping the case open and hooking in a real floppy drive. I then had to copy the contents of the extracted chipset driver .exe onto two disks. The directory structure is something like this... IDE\WinXP\RAIDTOOL \SATA_IDE \SATARAID \Floppy \Disk1 \NvRCoEnu.dll \disk1 \nvgts.sys \nvide.nvu \nvraid.cat \nvraidco.dll \nvrd32.inf \nvrd32.sys \txtsetup.oem \Disk2 \NvRCoAr.dll \NvRCoCs.dll \NvRCoDa.dll \NvRCoDe.dll \NvRCoEl.dll \NvRCoEng.dll \NvRCoEs.dll \NvRCoEsm.dll \NvRCoFi.dll \NvRCoFr.dll \NvRCoHe.dll \NvRCoHu.dll \NvRCoIt.dll \NvRCoJa.dll \NvRCoKo.dll \NvRCoNl.dll \NvRCoNo.dll \NvRCoPl.dll \NvRCoPt.dll \NvRCoPtb.dll \NvRCoRu.dll \NvRCoSk.dll \NvRCoSl.dll \NvRCoSv.dll \NvRCoTh.dll \NvRCoTr.dll \NvRCoZhc.dll \NvRCoZht.dll \disk2 The contents of disk1 and disk2 folders combined is slightly larger than the size of a floppy disk. The problem with integrating these into an nLited CD is that the second directory doesn't contain any .inf files. I'm assuming this second folder (disk2) is required because as I said when I did a normal attended install I was asked to insert disk2, and this worked in the end, e.g. no BSOD. So my question is this... how can I integrate a two disk textmode driver package into an nLited bootable CD? Or is there a way of stripping out the second disk requirement from the driver (because I guess I only need the english DLL really) by maybe hacking the txtsetup.oem and the inf file? Thanks - Sid
×
×
  • Create New...