Jump to content

gpwolfe

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About gpwolfe

gpwolfe's Achievements

0

Reputation

  1. As I said in my original post, I did that. Observe: I did all the steps in my first post several times w/no success. The latest bit of information about the 6.56 drivers seems promising. I will be grabbing 2 new Raptors today so I should be able to try that out this weekend. Thanks.
  2. What are you some kind of troll? One should never feed them, but I must in this case. You are an id***. I posted my process, show me where the issue is fanboi? Spewing useless drivel as you have done and then stating that it is not the OS but my fault is not helpful _at all_. But thanks for playing.
  3. I mentioned that I tried that also. One more data point is that I am able to install the AMD 64 bit version of longhorn beta 1 flawlessly. What the hell is the deal with this POS OS?
  4. Greetings, Hardware: Asus a8n-sli deluxe 3GB RAM Athlon 64 X2 4400+ 2 37GB Raptors on nvraid as striped (Raid0) Procedure: 1) I upgraded the chipset drivers to v6.65 in preparation for the BIOS upgrade. These were the latest available for 32bit windows. 2) Rebooted to make certain my current windows install wasn't horked. All was well. 3) I updated the BIOS to 1013...latest available. Asus' upgrade notes said to upgrade to v6.65 or later of the chipset drivers. 4) Rebooted to, again, confirm all was well w/current installation. All was, indeed, well w/current install. Downloaded the AMD 64 bit windows nforce4 chipset drivers from nvidia's site. The version they have is v6.66. Extracted the archive, which extracted to: nForce4_amd_6.66_winxp64_international Note that on nvidia's site there's no mention of international versus non international for this particular download. I also grabbed the 64bit display drivers from them as well. On that download page there are 2 options, "normal" and "international". I copied all the files in nForce4_amd_6.66_winxp64_international/IDE/WinXP/sataraid to a freshly formatted floppy. 5) Booted off of 64bit xp cd and pressed the "any" key to start the installer. 6) Pressed F6 when appropriate. 7) Inserted floppy disk w/nvraid drivers on it into floppy drive. 8) Pressed 's' where it asks to install storage drivers. 9) Pressed return. 10-12) Selected the storage driver first. (2nd choice in list.) I had read before that for some reason they were listed incorrectly. This data is old and could be incorrect. However it doesn't seem to matter for my issue as I've tried all permutations of the damnable loading order. 13) Pressed return. 14) Pressed return. This is the part where it says to press return/enter to setup windows. 15) Pressed F8; EULA bit. 16) It found the RAID drive 17) Selected it and pressed return. 18) Selected NTFS (quick) and pressed return. 19) It formats to 20% and hangs. Here's where I'm at a loss on what the hell the issue is. It seems to have something to do w/64bit xp. If I'm really quick with the driver loading bits above it will make it to where it's loading idecoi.dll off of the floppy. But then it hangs w/floppy LED ON...I've waited 20 minutes and it doesn't progress so it's not just "sluggish". I've tried the driver integration bit following the nlite 1.0b4 as the guide on this forum suggests. That part seems to have gone well as it detects the raid volume just as if I had gone through the F6 method manually. It also gets a bit further into the install. It all seems really timing dependant, like I've got only 1 minute of use before the thing hangs. I've broken out the raid set into discrete drives and tried letting xp install to it with the default ide drivers. It sees the drive but I get the same thing. If I doddle whilst doing stuff it hangs on formatting. Otherwise it hangs during copying of files. I've reburned the disk at the slowest speed my notebooks supports (8x) and still no love. I saw someone mention to not have any USB devices plugged in on the unattended nlite nv drivers forum. I had a USB mouse plugged in so I removed that. And, yet, still no love. I can plop in the xp pro sp2 32bit windows and it works just fine. With the 32 bit raid drivers, or with the raid set split using the stock ide drivers. I've installed 64bit Gentoo 2005.1 on the thing w/no issues. All signs point to the 64bit XP being fux0r3d either this build or my specific collection of bits...but I haven't found anyone else having the problem(s) I'm having. What gives? Please help. Thanks, Gary
  5. I've used the F6 install method with the drivers from Asus site and the disk made both by hand, and via their makedriverdisk.exe applet. It loads the drivers off of the disk just fine, and I can get to the point where I see the striped drive (2 36GB raptors in a stripe set). I can partition and format it w/no errors. After this part the trouble starts. After the formatting it says that it's "building a list of files to copy" or the like and then throws up an error saying that "setup could not copy: nvatabus.sys". WTFO? It could load it off of the floppy to get to this point in the first place so everything should be great with the floppy drive, the cable, and the disk itself. Yet it refuses to copy it over at this point. So what's the problem now? The only way past that is to press [ESC] multiple times, every file it needed to load off of the floppy it reports that it cannot do so. After getting past all the drivers off of the floppy it copies everything off of the cdrom drive just fine. When it boots I get a panic because of the drivers not being copied. I do not understand, what the deal is with the above and have not found anyone who has had the problem, provide a solution. This *VERY* issue is the whole point of trying to integrate the drives onto the xp install media. Right now I cannot get windows on this machine, using RAID, w/this motherboard. It's very irritating.
  6. As directed, I'm posting this here, and to the other "[issue]" topics. I used a plain vanilla xp pro cd as my base and moved in this progression: vanilla xp pro -> sp2 slipstreamed -> all bts driver packs via option 2. All integration/slipstreaming went flawlessly. The resulting image burns and boots w/no issues. It results in a STOP 7b BSOD during text mode. I don't even get to the partitioning part. In the, now closed, forum you had requested my PCI IDs for the nforce 4 and siI3114 controller. I'm using an a8n-sli deluxe nforce4 pro based motherboard. I've tried with drives on the siI3114 controller, and the nforce controller with, and without, the siI3114 disabled in bios. The same STOP 7b results in each instance. The IDs, as taken from the drivers are: siI3114 PCI\VEN_1095&DEV_3114&SUBSYS_71141095 PCI\VEN_1095&DEV_3114&SUBSYS_81361043 nforce4 sata/ide PCI\VEN_10DE&DEV_008E PCI\VEN_10DE&DEV_0085 PCI\VEN_10DE&DEV_00D5 PCI\VEN_10DE&DEV_00EE PCI\VEN_10DE&DEV_00E3 PCI\VEN_10DE&DEV_00E5 PCI\VEN_10DE&DEV_0035 PCI\VEN_10DE&DEV_0036 PCI\VEN_10DE&DEV_003E PCI\VEN_10DE&DEV_0053 PCI\VEN_10DE&DEV_0054 PCI\VEN_10DE&DEV_0055 Any assistance would be greatly appreciated. Thanks.
  7. As directed, I'm posting this here, and to the other "[issue]" topics. I used a plain vanilla xp pro cd as my base and moved in this progression: vanilla xp pro -> sp2 slipstreamed -> all bts driver packs via option 2. All integration/slipstreaming went flawlessly. The resulting image burns and boots w/no issues. It results in a STOP 7b BSOD during text mode. I don't even get to the partitioning part. In the, now closed, forum you had requested my PCI IDs for the nforce 4 and siI3114 controller. I'm using an a8n-sli deluxe nforce4 pro based motherboard. I've tried with drives on the siI3114 controller, and the nforce controller with, and without, the siI3114 disabled in bios. The same STOP 7b results in each instance. The IDs, as taken from the drivers are: siI3114 PCI\VEN_1095&DEV_3114&SUBSYS_71141095 PCI\VEN_1095&DEV_3114&SUBSYS_81361043 nforce4 sata/ide PCI\VEN_10DE&DEV_008E PCI\VEN_10DE&DEV_0085 PCI\VEN_10DE&DEV_00D5 PCI\VEN_10DE&DEV_00EE PCI\VEN_10DE&DEV_00E3 PCI\VEN_10DE&DEV_00E5 PCI\VEN_10DE&DEV_0035 PCI\VEN_10DE&DEV_0036 PCI\VEN_10DE&DEV_003E PCI\VEN_10DE&DEV_0053 PCI\VEN_10DE&DEV_0054 PCI\VEN_10DE&DEV_0055 Any assistance would be greatly appreciated. Thanks.
  8. Greetings, I downloaded the bts v503.2 base and all the v503 packs. I ran the updater and it said I had the latest version of everything. I followed your tutorial and the instructions. Everything integrated and ran smoothly. vanilla xp pro -> sp2 slipstreamed as a base. I made the CD, booted, it started to load the drivers in the textmode setup of XP. Then BSOD STOP 7b. I don't even get to the point where I can partition the drives. My setup is an Asus a8n-sli deluxe which is based on the nforce 4 chipset. I have 2 Western digital raptors on the nforce SATA ports w/raid mode enabled in the BIOS. I have them configured in the nforce raid config (F10) as a stripe set. I've tried them on the sil3114 controller as well w/no love that way either. Any ideas? Thanks, Gary PS One other thing, on a vanilla xp pro CD if I press F6 during installation and use a floppy to load the nvatabus and nvraid drivers I get to the point where I can see the striped drive. However, when it goes to "make a list of files to copy" and tries to copy it comes up and says that setup cannot load file: nvatabus.sys. And gives me the option to quit (f3), or try again, or skip the file. Ultimately only skipping the files gets me past this part. Then the files copy ok. Obviously it tanks on the reboot because the driver files aren't there. The question is what the hell is the deal with setup not being able to copy the drivers from the floppy? It can read the disk just fine and the files can't be corrupted because it loaded them w/out issue to be able to see the raid set and copy data to it. And, it should go to follow, that the floppy drive, cable, and such should also be swell. I'm completely fux0r3d, as it were, at this point. Anyone have/solve this issue?
  9. Thanks for responding. I tried your suggestion and as it happens, yes, the entries are the same as what I would type from the commandline to get the things to install. I did try a different approach though. I took all these things that haven't been installing, put them into another .cmd script. I added an entry towards the end of the RunOnceEx.cmd that copies this script to the ...\all users\programs\startup folder. Upon booting back up, it runs and these things install fine. At the end it starts a shutdown timer and then deletes itself. "these things" has to be qualified as everything except the 3dmark bits. I'm thinking that they won't install unless/until the video drivers are installed. That seems to be the deciding factor on whether 01se will install or not. As I said before I have not ever been able to get 03 to install silently. I tried a few other things like MagicIso, for some reason it didn't like to install from the RunOnceEx method either. It works fine from the startup script though. At this point, I just want to get this thing finished, I'm ok with this odd method. In fact just for collectiveness I am going to forego installing anything via the RunOnceEx method. I'll just fork a script to copy over this startup script to it's dest and install everything from there. Seems a bit more reliable in general, for me anyway. It's irritate because I like the nifty itinerary windows puts up when things are done from the registry. Though, in the end, I guess I'll take functionality over form. --Gary
  10. Greetings, I've read the guide and created my unattended installation DVD. Most everything works just fine. The problem I'm running into is that some entries in the RunOnceEx.cmd file, on reboot (when they actually attempt to install), seem to just get glossed over. For instance I've not been able to get 3dmark2001se, vmware, or vpc2004 to install. They come up in the itinerary but are only bold/active for a brief moment and then it skips down to the next entries. At first I thought I had a path problem/typo or a bad switch. However, I can install all of these things from command line silently just fine. This is, obviously, on an existing installation of windows which isn't so helpful in this instance. Any ideas? Thanks, --gpwolfe Just for completeness here are the entries from my RunOnceEx.cmd file: REG ADD %KEY%\011 /VE /D "VMWare workstation 4.5.1 build 7568" /f REG ADD %KEY%\011 /V 1 /D "%systemdrive%\install\apps\vmware_workstation_451-7568\vmware451-7568\VMwareWorkstation.msi /qn" /f REG ADD %KEY%\130 /VE /D "3dmark 2001se build 330" /f REG ADD %KEY%\130 /V 1 /D "%systemdrive%\install\apps\3dmark2001se\setup.exe -s" /f REG ADD %KEY%\172 /VE /D "Microsoft Virtual PC 2004" /f REG ADD %KEY%\172 /V 1 /D "%systemdrive%\install\apps\microsoftvpc2004\setup.exe /S /v/qn" /f Oh, and I would like to be able to get 3dmark2003 installed silently as well but I can't seem to manage that even on an already installed xp. here's what I've tried: REG ADD %KEY%\125 /VE /D "3dmark03 build 340" /f REG ADD %KEY%\125 /V 1 /D "%systemdrive%\install\apps\3dmark2003\3dmark03.exe -s" /f That seems to be silent, no dialogs/requestors, but nothing is actually installed. Thanks again.
×
×
  • Create New...