DriverPacks.net Forum - How Can DÄ±sable OEM folder

Re: How Can DÄ±sable OEM folder

null@example.com (hose_antonio) — Fri, 23 Jan 2009 08:09:20 +0000

OverFlow wrote:

if you cant answer simple questions like telling us the version number.
And it is obviously not the most recent as you said - don't lie to us - we know better.
(or providing your base log which is almost always required for support) I will close this thread.
modifying the presetup file is also not supported, and your version above is not valid at all and won't even be called.
Post your log.
Moved to other

Ä± dont know speak englÄ±sh very well Ä±m student and Ä±m not said lie ok if you know better than from me Ä±ts possÄ±ble and Ä± solved my problem Ä±nstalled masstorage fÄ±le manuel from msfn on this topic
http://www.msfn.org/board/index.php?showtopic=13173
thanks

Re: How Can DÄ±sable OEM folder

null@example.com (OverFlow) — Thu, 22 Jan 2009 23:53:08 +0000

if you cant answer simple questions like telling us the version number.
And it is obviously not the most recent as you said - don't lie to us - we know better.

(or providing your base log which is almost always required for support) I will close this thread.

modifying the presetup file is also not supported, and your version above is not valid at all and won't even be called.

Post your log.

Moved to other

Re: How Can DÄ±sable OEM folder

null@example.com (hose_antonio) — Thu, 22 Jan 2009 16:13:32 +0000

OverFlow wrote:

What version of DriverPacks BASE are you useing?

last versiyon and Ä± modÄ±fype presetup.cmd

Re: How Can DÄ±sable OEM folder

null@example.com (OverFlow) — Thu, 22 Jan 2009 12:32:50 +0000

What version of DriverPacks BASE are you useing?

Re: How Can DÄ±sable OEM folder

null@example.com (hose_antonio) — Thu, 22 Jan 2009 10:20:39 +0000

Ä± used driver from cd Ä± dont know how can Ä± manuel Ä±nstall masstorage fÄ±le or how can ddÄ±sable oem folder an bpbase finisher and fÄ±les

my cd root

and my presetup.cmd fÄ±le

REM +=======================================================+
REM | Comment out what you don't need. These are mostly |
REM | examples to give you an idea of how it all works. |
REM +=======================================================+

REM +=======================================================+
REM | Finding CDROM driveletter |
REM |-------------------------------------------------------|
set tagfile=\WIN51
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 z) do if exist "%%i:%tagfile%" set CDDRIVE=%%i:
REM +=======================================================+

REM +=======================================================+
REM | We should be already in system32, this is just to be |
REM | sure |
REM |-------------------------------------------------------|
%SystemDrive%
cd %SystemRoot%\system32
REM +=======================================================+

REM +=======================================================+
REM | Trick Windows into identifying the original setup.exe |
REM | deleting the setup.exe will not work, just rename it |
REM |-------------------------------------------------------|
if exist setup.exe ren setup.exe setupold.exe
if exist setupORG.exe ren setupORG.exe setup.exe
REM +=======================================================+

%CDDRIVE%\Driver\SetDevicePath.exe %CDDRIVE%\driver
start %CDDRIVE%\driver\WatchDriverSigningPolicy.exe

REM +=======================================================+
REM | Finally start the installation with the originally |
REM | given parameters |
REM |-------------------------------------------------------|
start /WAIT setup.exe %*
REM +=======================================================+

Re: How Can DÄ±sable OEM folder

null@example.com (OverFlow) — Wed, 21 Jan 2009 23:25:06 +0000

Outbreaker wrote:

If you choose only "DriverPack MassStorage text mode" and you have SATA/AHCI option on in the BIOS then you get a Bluescreen after the first Windows XP loading screen.

This is because if you only slipstream textmode drivers then the Plug and Play drivers are not available to WinPE or Windows (Since you did not include them) so it will BSOD. Some drivers don't need thier PnP counterparts, these will work fine (Like IDE drivers). I recomend useing mass text and regular mass as a set.

If you only select mass textmode no OEM folder is created.
(it is not neccessary to select custom for the finisher. if no packs are selected the finisher will not be added )

The simple answer is "You can't add DriverPacks and not end up with an OEM folder"
UNLESS... You don't plan on supporting mass storage drivers that will require their PnP counterparts.

Re: How Can DÄ±sable OEM folder

null@example.com (hose_antonio) — Wed, 21 Jan 2009 20:06:27 +0000

@Echo_Platoon Ä± tried but dpbase create oem folder again how can pass this

Re: How Can DÄ±sable OEM folder

null@example.com (Outbreaker) — Wed, 21 Jan 2009 16:27:14 +0000

If you choose only "DriverPack MassStorage text mode" and you have SATA/AHCI option on in the BIOS then you get a Bluescreen after the first Windows XP loading screen.

Re: How Can DÄ±sable OEM folder

null@example.com (Echo_Platoon) — Wed, 21 Jan 2009 14:54:26 +0000

hose_antonio wrote:

I dont want to oem folder Ä±n my unattandet cd Ä± just want to masstorage driver fÄ±le Ä±m Ä±386 folder Ä± dont want dpbase create oem folder how can Ä± dÄ±sable create oem folder

To get it to not create an OEM folder, you have to choose the following settings:

1. Choose only "DriverPack MassStorage text mode" when choosing what DriverPacks you want to integrate.
2. "method 2" for slipstream method
3. "Custom" for the method to start the Finisher and just click OK on the pop-up you get when choosing "Custom"
4. Disable KTD
5. Enable QSC

I just tested this on a Windows XP Professional with SP3 source. The integration was successful and no OEM folder was created.

How Can DÄ±sable OEM folder

null@example.com (hose_antonio) — Wed, 21 Jan 2009 13:46:43 +0000

I dont want to oem folder Ä±n my unattandet cd Ä± just want to masstorage driver fÄ±le Ä±m Ä±386 folder Ä± dont want dpbase create oem folder how can Ä± dÄ±sable create oem folder