Search options (Page 211 of 213)

here is some insight

this card is supported by the OS directly.

there is an update on the microsoft update site for this driver too.

i run into this all the time in VMWare (it emulates this cards hardware for its "sound card")

the only way i have gotten it to work (so my music plays in WPI - a must have!!!)  is to use method 1.

then i manually call the VMWare Tools setup from  Runonceex.cmd

@ECHO OFF

for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i:
set wpipath=%drive%\wpi

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY%\999 /V 1 /D "%SystemDrive%\DPsFnshr.exe"
REG ADD %KEY%\999 /V 2 /D "%wpipath%\Install\vmw\VMTools.msi /quiet /norestart"
REG ADD %KEY%\999 /V 3 /D "%wpipath%\WPI.hta" /f

EXIT

you could call the sound blaster setup program where i call the VMTools.msi and "fix" the problem

(i leave this line in for all my disks as the VMTools exits silently if its not a VMWare shell)

Third party DL programs typicaly will not work (some do) since our server checks for the refering site.
Try plain old IE and see if it works.
If yes then your DLer or Browser is not compatible with our DL site.

If you use this code you dont need to create a CD.TXT file

for /f "delims=: tokens=1" %%i in ("%~dp0") do set CDROM=%%i:
SET CDDRIVE=%cdrom%\$OEM$

If you need to know what the meaning or purpose is for a certain entry, you can find a reference in any DriverPacks BASE starting from version 7.01.2 RC1, in docs\DriverPack_reference_wnt5_x86-32.ini.

It is my understanding that all packs will be required to have these in the future.
For most third party packs exceptions probably won't be an issue so it should be fairly easy to create them.

If a partition is not deleted that contained an NT OS then the boot.ini could be appended.
Please verify that your install deletes existing partiton information from the disk then repartitions and reformats (quick is fine).
Are there other windows installations present in the machine? Are you useing the built in partitioning / formating from the windows install?

for wpi i use this combo and dont have issues with the two running together.

use rvm to Update source
nlite make all changes leave open at the create iso screen
Run dpbase with mode 1 & guirunonce

you might do some editing so it looks similar to this.

CMDLines.txt

[COMMANDS]
"regedit /s theme.reg"
Runonceex.cmd
"rundll32 advpack.dll,LaunchINFSectionEx nLite.inf,U,,4,N"

Runonceex.cmd

@ECHO OFF

for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i:
set wpipath=%drive%\wpi

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY%\999 /V 1 /D "%SystemDrive%\DPsFnshr.exe"
REG ADD %KEY%\999 /V 2 /D "%wpipath%\Install\vmw\VMTools.msi /quiet /norestart"
REG ADD %KEY%\999 /V 3 /D "%wpipath%\WPI.hta" /f

EXIT

As far as the quotes go

They are only needed for long filenames or paths with spaces ect...

hope this helps.... doesnt seem to me to be an issue with driverpacks? do you still get the dupes with no DP applied to the build?

We are very close to having a guide together to help with basic questions.

i like and use nLite myself. but you need to not make any changes to your source folder with nlite AFTER you run the DriverPacks Base

Make all your nlite config options and when you get to the make iso screen minimize that and run DP Base with whatever options you  wish then when it completes restore the nlite window and create iso.

This is just a basic outline of course, but should get you going.

I run nLite RyanVM and full driverpacks install and it weighs in at 700meg and fits perfectly on a cd
So I think you are adding something else too? or not deleteing something?

but... looks like you use nvidia graphics so you could not select Graphics B and save 50 meg
and you dont have wireless lan either so you could not select that for a savings of another 20.
Realtek sound is in pack A so you could kill Sound B and save another 45.

again im more interedted in why it doesnt fit when it should fit perfect

If its OK with Helmi its all good with me!

although, as he said..

A shorter post with a link wouldn't have gotten my attn.
AND he only had one post here at that time too.

I agree with useing a Virtual Machine first. Microsoft VM is free and VMWare has a free trial.

I have seen this error when useing the OemPreinstall=Yes in winnt.sif and an f6 driver is used.

It seems to me you are not really slipstreaming a disk install, this describes more of a RIS type installation.

Try reading this topic and see if it helps http://forum.driverpacks.net/viewtopic.php?id=641

looks like its PCI\VEN_8086&DEV_2997&CC_0700 but this actually looks like a serial device

It is probably for an optional remote management fuction - serial over lan - I put this with the 3rdParty plugins.

get it here --> http://3rdpartydriverpacks.thesneaky.co … -32_1.0.7z

Yes! Thanks to your time, interest and contribution it is now part of the driverpacks.
I don't know if it will make it to one of the main packs, that will be up to Bâshrat the Sneaky.