Hi tcntad... Yeah the pass in the txt file in this thread is only for the OEMBios files... the pass for the OEMsp3 are not in this thread at all? even tho you mention the oemsp3 uploads here... Took me yonkies to find it dude and very misleading.. Great work tho, thanks for your efforts, great stuff....
Most probably it must be related to WINNT.SIF file...I think driverpacks entry in the winnt.sif file is somehow deleted or corrupted...Have you followed the correct steps?..
Hmmm..Well,Still I do think you should check your Winnt.sif file...or else may be in rare case the sata drivers for that laptop may not be present in the mass storage driverpack..
I will check that too I just find it weird if the drivers woudnt be there:/, I can download and integrate from HPs website instead. Edit: I can check my august dvd.. but after a update of the mass storage drivers there is a known issue at windows installation, and it seems to be the problem i have. a missing nrvdblabla.sys file cant be found.
Is it possible to include such a feature that, if I install this multioem XP in a pc, which has no SLP string in its bios/dmi, then it automatically installs the default oembios set of XP SP3 VL and install a genuine XP VL key or promts user to input a key???? If possible, let us know...
well this is for OEM:SLP only but im sure its not that hard i guess.. altho i woudnt know why you would have VL instead of OEM:SLP.. I understand corporations but then they have one image with that key and all other stuff to deploy..
Neither have i, but the problem is with the masstorage driverpack.. I also created a new thread at their forum, no replies yet.. I will try the same dvd and turn off satanative.. Appearently its a know issue and it says "dont click the button and installation will continue"... I just dont know which button not to click Edit: smarte pants has replied me.
Code: Nvrd32.sys file description Productname: NVIDIA nForce(TM) RAID Driver Description: NVIDIA® nForce(TM) RAID Driver Company: NVIDIA Corporation File size: Various This file is a chipset driver and needs to be installed via F6 Floppy during initial install. Not exactly nvrdblabla.sys...But i think it seems to be related to nvidia raid driver and thats the reason for that problem...just hope it will help you somehow...
Thank you for the reply! I am using the uncompressed oembios filesets for the Multi-OEM DVD. I'm using Method 2, which includes the use of driver packs. I am doing: 1) Extract all of my XP Pro OEM to a folder called XP Pro OEM 2) Copy/paste the uncompressed oembios (from the collection now stored online). 3) I then run RyanVM to integrate OnePiece Post-SP3 into the files. 4) I run driverpacks, selecting ALL drivers into the files 5) I run RyanVM, this time using the MultiOEM file 6) I run nite, but I only select create bootable ISO. I think my problem is this. When I run OEMSCAN on my laptop i get: "OEMBIOS Scanner v1.4.1 by Jeremy <xehqter> Reading BIOS Memory Matched: IBM CORPORATION Checking Authenticity of OEMBIOS files CAT file currupt: C:\Users\Guest\Desktop\XP_MULTIOEMv2.1\OEM\FILESETS\XP\D7A77612\OEMBIOS.CAT I think since my OEMBIOS files are currupt, it isn't activating correct. Although I have downloaded it multiple times from the server.
I'm sure you have done this already, but when you integrated with driverpacks, you selected Mass Storage, AND selected TEXT MODE Entry, which mimics the F6 option? When you select your packs its the waaay bottom of the list.
I pressed the "select all" option which inclues that one yep I got an idea by smarte_pants so ill try that one now.
You are doing all the steps but not in proper order... It should be as following.... * XP source should be extracted at the root of any partition such as C:\XPSource *Then you must integrate the xp updatepack in a seperate sesssion *Then if you want to integrate any other addon... *Then You must integrate Multi-OEM addon with RyanVM Integrator Only in a seperate session.. *Then Comes Driverpacks. * You can create an XP iso from the updated XP source with either Nlite or RyanVM..Both will work,..But don't do any other tweaks at the last stage..All the tweaking should be done before integrating the Multi_OEM addon.. Note: You can put the oembios filesets even after integrating the Multi-OEM addon.Just put them in the correct folders in the root of the integrated XP Source. It may be possible that the oembios fileset for IBM that you have got is corrupted..But you should not run oemscan from the desktop..It will not work..Oemscan only adds keys during windows install..
I will Smarte_pants said he would put together a testpack for me with masstorage drivers.. I have sofar tested diff. packs etc with no success yet. he also told me to edit the .ini file.. first few attempts did not work..sofar.