• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About rcordorica

  • Rank
    Windows Hacker
  • Birthday 04/05/1986

Contact Methods

  • AIM
  • Website URL
  1. Uh, I take back the last statement about this latest driver pack causing the windows install not to find the cd. It appears that there is a bug with integration using Nlite and some program package i may have used. I am going to test to find out what is causing the problem. I think I know where your going, using the TEXTMODE method (which I helped pioneer). I have since stopped using that method because I am trying to build a universal installl cd, but yes, the TEXTMODE method does work well if you plan to only integrate a few drivers.
  2. i just made my install cd almost exactly like yours and I also have the 250GB chipset. THe unintended install correctly found my RAID 0, but I could copy files to the drive due to a missing file. I think the latest release has some problems. I wish I had a more detailed error message, but all windows said was "cannot cotinue because cannot copy files from the CD, if you would like to retry press ENTER" I have an older cd using some older driverpacks that works just fine, so something has changed. What I did notice is that now the NVATABUS driver is being used for the standard IDE, which has my dvd drive on it. Maybe that is why the windows installation can't find my cd? Anyways, I am awaiting a fix too.
  3. I got the same problem today... I still haven't been able to make a working xpcd since 5.04.... argh. I really wan't to test the nvidia fix.
  4. where is the 5.04.4 masstorage? is it part of the basepack that needs to be updated? I want to test it.
  5. I will try it out today.. I was actually thinking the same thing last night because when I worked on the MASSTORAGE method with Trainee we had to figure out how to force the drivers into their correct directories.. The Dll's had a lot to do with it. I can say for sure that the nvidia drivers need all the dll's listed in their Txtsetup.oem file. Esentially they need to be copied to %systemdrive%/windows/system32 from what I remember. btw. Can I have a few gmail invites? I am excited about their new news.
  6. I tried something else just to check if it is a conflict with other drivers. I removed all entires to all other drivers except the nvidia and si311x drivers. I still got the BSOD. The only nvidia that works for me is my old Nlite .91 where I did my own MASSTORAGE, and also a more recent Nlite, but I still had to manually add entries into the txtsetup because Nlite doesn't know how to deal with more than one driver for a single device (like Nvidia!). blah, maybe my computer is pulling an april fools joke on me.
  7. I remade my XPCD today with your new 5.04.1 stuff. 1. It worked perfectly in Vmware. 2. On my real machine, it crashed right before getting to the partition manager. I got a BSOD with the 0x0...07b message. Same as before. Tested on Asus K8N-E Deluxe NVRAID using 2x160GB in Stripe 0. Perhaps latter I can test he 3114 for you, but right now I am more interested in fixing the NVRAID/NVATABUS. Something is conflicting with the system to make it crash.... I only wish windows errors were more discriptive. btw, my NVRAID bios was updated today to a new version when I applied a beta bios for my motherboard... I notice it is faster now, but I the BSOD error is still coming up. i really need a floppy drive to test out nvidia drivers myself... maybe the newer versions are just buggy.
  8. the way for somebody to try would to be to do a F6 install to see if windows boots fine. I can't help there because I don't have a floppy drive (that works). But, i think this mostly has to do with the driverpack's method. There are currently only two methods that work for me with si3114 and NVRAID. 1. The MASSTORAGE method (Rasor utility does this nicely). It takes more space, and is more work to set up initially, but after the first time, it's easy to simply copy over the old directories and a few lines into the winnt.sif. 2. Nlite's method is also interesting and seems to work fine if you only do a few drivers at a time. I successfully made a windows cd with si3114 and NVRAID with nlite doing the driver integration for me. It uses a completely different method where all the files get put into i386/NLDRV and it appends info in the txtsetup.sif. But, there is a bug where you have to add the missing entry for NVATABUS because Nlite misses that, even though the drivers get copied over fine. I think that maybe there are just too many drivers now and they are conflicting with each other. Method 1 always used to work for me if I went ahead and did some manual editing for the NVRAID. Recently, i have gotten Method2 to work for all other drivers, except masstroage. I think what needs to be done here is separate the troublesome drivers and do those with the MASSTORAGE method which seems to be the "microsoft" defined way of doing things. It shouldn't be too hard to copy the files over to $OEM$ and /i386/$OEM$ while still using Method 2 for example. I have sucessfuly combined 3 different methods on one cd without any problems.
  9. in one of your older driverpacks it worked fine for me, so something got changed and messed them up. (actually, the nvidia never worked. but the si3114r did).
  10. alright, i'm editing the txtsetup.sif right now. i'll report back EDIT: OKAY, some results: i removed all entries to Nvidia (ck8, nvatabus, nvraid, etc..) in txtsetup.sif. 1. With NVRAID enabled in bios, the hard drives on the si3114 were correctly found, and I did not get the BSOD right before the partition manager. 2. With NVRAID disabled in bios, the hard drivers on the si3114 were correctly found, and I did not get the BSOD right before the partition manager. 3. With NVRAID still disabled, i formated the hard drives as 128K stripe 0 on the si3114, and tried to reinstall windows. I got through the intial format and cd copying to the computer. However, upon reboot when the GUI portion of the windows installer was about to start, I got a BSOD: Unmountable_boot_volume or something similar to that. So? What is the problem. I am confused. Becuase removing the nvidia got me past one error, but now I got another error. (typing this from good ol' trustly linux)
  11. yeah, ok. I just tried the completely redone cd and it still gave the same error. I posted this before, but i guess you missed it. http://www.msfn.org/board/index.php?showto...ndpost&p=284751 ok, my board is an Asus K8N-E Deluxe It has Si3114r: I am running two hard drives in Raid 0 Device Instance Id: PCI\VEN_1095&DEV_3114&SUBSYS_81361043&REV_02\4&22775069&0&6070 HardWare Ids: PCI\VEN_1095&DEV_3114&SUBSYS_81361043&REV_02 PCI\VEN_1095&DEV_3114&SUBSYS_81361043 PCI\VEN_1095&DEV_3114&CC_010400 PCI\VEN_1095&DEV_3114&CC_0104 Compatible Ids: PCI\VEN_1095&DEV_3114&REV_02 PCI\VEN_1095&DEV_3114 PCI\VEN_1095&CC_010400 PCI\VEN_1095&CC_0104 PCI\VEN_1095 PCI\CC_010400 PCI\CC_0104 NVRAID: Device Instance Id: ACPI\_NVRAIDBUS\3&267A616A&0 Hardware Ids: ACPI\_NVRAIDBUS *_NVRAIDBUS NVATABUS: Serial ATA Controller Device Instance Id: PCI\VEN_10DE&DEV_00E3&SUBSYS_813F1043&REV_A2\3&267A616A&0&50 Hardware Ids: PCI\VEN_10DE&DEV_00E3&SUBSYS_813F1043&REV_A2 PCI\VEN_10DE&DEV_00E3&SUBSYS_813F1043 PCI\VEN_10DE&DEV_00E3&CC_010185 PCI\VEN_10DE&DEV_00E3&CC_0101 Compatible Ids: PCI\VEN_10DE&DEV_00E3&REV_A2 PCI\VEN_10DE&DEV_00E3 PCI\VEN_10DE&CC_010185 PCI\VEN_10DE&CC_0101 PCI\VEN_10DE PCI\CC_010185 PCI\CC_0101 Nvidia Parallel ATA Controller: Device Instance: PCI\VEN_10DE&DEV_00E5&SUBSYS_813F1043&REV_A2\3&267A616A&0&40 HardWare: PCI\VEN_10DE&DEV_00E5&SUBSYS_813F1043&REV_A2 PCI\VEN_10DE&DEV_00E5&SUBSYS_813F1043 PCI\VEN_10DE&DEV_00E5&CC_01018A PCI\VEN_10DE&DEV_00E5&CC_0101 Compatible: PCI\VEN_10DE&DEV_00E5&REV_A2 PCI\VEN_10DE&DEV_00E5 PCI\VEN_10DE&CC_01018A PCI\VEN_10DE&CC_0101 PCI\VEN_10DE PCI\CC_01018A PCI\CC_0101 btw, something changed to cause this BSOD because I have a slighty older version of an XPCD with your drivers using Method 2 and it worked perfectly. Except at that time NVRAID didn't work. EDIT: I also thought of something else. I just realized that The first time I got the BSOD, i only had the NVRAID working. I had disabled the si3114 in the bios because I wasn't using it. Now I am on the si3114, and have the NVRAID disabled, and it still gave me the BSOD. That leads me to believe perhaps something is wrong with another driver.
  12. I got the same error! I thought it was my fault.... well, i am trying to make a new iso right now. i'll report back
  13. you can do what rgreen said and make sure that the older nvidia drivers are removed so that windows next best choice is your non whql certified drivers. Or, get the newest whql lab drivers and windows will automatically install them.
  14. it still doesn't work i made an nlite cd. Windows Original -> SP2 -> Update Pack -> WMP 10 integration -> Driverpacks (masstorage, graphics, lan, wlan, base). the cd installed perfectly under vmware. Except for a weird error about missing "RD" after the installation had finished on the first windows run. But I clicked OK and everything was perfect. however, when I tried to install it on my native machine, it crashed. This is right before the text based installation is about to start "Windows is starting" or something like that. In my winnt.sif I have it set to automatically go to the partition manager and skip everything else. I think i noticed you using Nforce3 drivers. Maybe you need a new version? Well, here is the picture of the error. I tried changing my bios settings and nothing worked. I am not overclocking. System Specs: Athlon64 3200+ Nforce3 250GB Asus K8NE-Deluxe Using NVRAID/NVATABUS RAID Stripe 0, 2x160GB
  15. @bashrat - have you fixed method 2 for the masstroage yet? How about Nvidia drivers (nvatabus/nvraid)? The reason I ask is because the last time I tried your driverpack under method 2 it simply rebooted upon the first GUI installation screen. I have never gotten method 2 to work. And method 1 works, but the Nforce drivers have always required me to force the nvatabus with the MASSTORAGE method. thanks