Topic: How Can Dısable OEM folder
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
You are not logged in. Please login or register.
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
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.
Last edited by Echo_Platoon (2009-01-22 02:25:09)
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.
@Echo_Platoon ı tried but dpbase create oem folder again how can pass this
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.
ı 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.exeREM +=======================================================+
REM | Finally start the installation with the originally |
REM | given parameters |
REM |-------------------------------------------------------|
start /WAIT setup.exe %*
REM +=======================================================+
Last edited by hose_antonio (2009-01-22 21:53:56)
What version of DriverPacks BASE are you useing?
What version of DriverPacks BASE are you useing?
last versiyon and ı modıfype presetup.cmd
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
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
Last edited by hose_antonio (2009-01-23 19:44:23)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.015 seconds, 11 queries executed ]