1 Reply by johnye_pt

(2 replies, posted in Feedback and Support - DriverPacks Base)

mr_smartepants wrote:

Your first "for" loop is missing the end-quotes.  Change to read as below:

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:\CD\WXPS\OEM" SET "CDDRIVE=%%i:\CD\WXPS" & GOTO DPsFound
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO DIR %%i: && IF EXIST "%%i:%TAGFILE%" SET "CDDRIVE=%%i:" & GOTO DPsFound
IF EXIST "\$win_nt$.~ls" SET CDDRIVE=\$win_nt$.~ls
:DPsFound

Thanks, I also noticed that last night but could only test it this morning. Tested and working wink

Go to forum: Feedback and Support - DriverPacks Base

2 Topic by johnye_pt

(2 replies, posted in Feedback and Support - DriverPacks Base)

Hi. I'm building a CD that contains CD\WXPP (normal XP), CD\WXPN (nLited XP) and CD\WXPS (nLited XP + DriverPack Mass Storage 11.11). For that to work I copied the I386 folder from each CD folder to the root, renamed each one to the same names above (WXPP, WXPN, WXPS), patched SETUPLDR.BIN, TXTSETUP.SIF and boot file accordingly and used cdshell as boot loader.

They all install fine in Virtual PC except for WXPS because the drivers/files/folders are not where the batches expect them to be. If I make an ISO of the WXPS folder (all files/folders in root as expected) it installs fine, because I can see the progress bar at the beginning of the GUI mode and at first boot.

I already know that CD\WXPS\I386\presetup.cmd and CD\WXPS\OEM\DP_Install_Tool.cmd must be edited, but I don't know if there is any other file I should edit. So far I made the following changes to the 2 batches, but with no success (no progress bars during installation).

CD\WXPS\I386\presetup.cmd and WXPS\presetup.cmd, added 1 line after the SET command:

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:\CD\WXPS\OEM SET CDDRIVE=%%i:\CD\WXPS & GOTO DPsFound
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:& GOTO DPsFound
:DPsFound

CD\WXPS\OEM\DP_Install_Tool.cmd and WXPS\OEM\DP_Install_Tool.cmd, added 1 line before the last IF:

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO (
 IF Exist "%%i:\OEM\bin\un7zip.exe" SET "DPLoc=%%i:\OEM" & Set "M=2"
 IF Exist "%%i:\$OEM$\$1\D\"   SET "DPLoc=%%i:\$OEM$\$1" & Set "M=1" & %%i
 IF Exist "%%i:\CD\WXPS\OEM\bin\un7zip.exe" SET "DPLoc=%%i:\CD\WXPS\OEM" & Set "M=2"
 IF "%M%">="1" GoTo Found)

Any help would be very appreciated wink

Go to forum: Feedback and Support - DriverPacks Base

3 Reply by johnye_pt

(3 replies, posted in Feedback and Support - DriverPacks Base)

Sorry, i know how annoying it can be when someone asks for something that has already been answered in a FAQ, i used to support a mIRC channel with a page and a Bot that had all the answers but somehow there was always someone repeating the same questions over and over again (read the fracking topic for once!). I searched for ms_1_exc_disableIfOS but somehow missed your FAQing topic in the answers wink

Thanks once again!

By the way, did anyone found out a more permanent solution for the Windows 2000 sATA driver limit problem? I see that the pack is still the same version as the topic i mentioned.

I know a more complicated solution, that would be dividing the current sATA driver package in two, create 2 different Windows 2000 folders (Windows 2000 + 1st sATA pack, Windows 2000 + 2nd sATA), then create a CD with a boot menu to select between the 2. I think there is a ISO handling program that creates the menu and the ISO without repeating identical files, so the 2 Windows would be 1GB on HDD but only about 600MB on CD. That way, all drivers would be included, but on 2 seperate Windows installations

Go to forum: Feedback and Support - DriverPacks Base

4 Topic by johnye_pt

(3 replies, posted in Feedback and Support - DriverPacks Base)

Hi. I was just reading http://forum.driverpacks.net/viewtopic.php?id=3433, the problem about  ahci7xx.sys corrupted during Windows 2000 installation, and the solution was adding ms_1_exc_disableIfOS="w2k" to a few drivers without it. I have a couple of questions:

1. What is the difference between exc_disableIfOS="w2k", exc_skipIfOS="w2k" and exc_replaceifOS="w2k"?

2. exc_disableIfOS="w2k" <=> ms_count=0 <=> removing the entire ms_ entry from the file?

Thanks in advance for taking the time to help me get a little bit smarter wink

Go to forum: Feedback and Support - DriverPacks Base

5 Reply by johnye_pt

(7 replies, posted in DriverPack Mass Storage)

Thanks, i didn't saw your links, i went to the tutorials at the main page but all it had was a german tutorial. Anyway, drivers slipstreamed and ready to go! smile

Go to forum: DriverPack Mass Storage

6 Reply by johnye_pt

(7 replies, posted in DriverPack Mass Storage)

Samuca1300 wrote:

Hello all smile

I want to integrate the Sata/Raid drivers pack only on xp sp3.
Is it enough to integrate MassStorage pack only for text mode or do I have also to integrate the other standard way?

I'm also trying to slipstream sATA drivers to Windows XP SP3 text mode setup with nLite, by extracting DP_MassStorage_wnt5_x86-32_901.7z to a folder and then adding it with nLite's option to insert "Multiple Driver folder", but all it inserts are PNP drivers. With DP_MassStorage_wnt5_x86-32_805.7z, it asks me if i want PNP or Textmode drivers but just for Smart Array Controllers (D\M\C1) and Intel Controllers (D\M\I3).

Does your DriverPacks BASE program slipstreams drivers to Windows XP SP3 text mode?

Go to forum: DriverPack Mass Storage