Search options (Page 68 of 213)

Excellent first post pkzero!

Pack versions, HWIDs, Links... very nice!

Welcome to DriverPacks.net

Wayne,

Please remember that PE is NOT an OS, It's not windows.
It's an installation tool (and thanks to Bart also a repair tool) not an OS substitiute.

IF you want full blown windows performance you need to install windows.
for example mass storage drivers are the Text Mode drivers ONLY... (16 bit)
not the good PnP performance drivers, etc... PE will not reach the performance levels of the full OS, it can't.

You are not going to be able to play DOOM / Crysis from PE any more so than you could from safe mode. In fact you may have better luck from safemode You will be able to run a virus scan

From your finisher log...

2009-12-07 16:50:51 : <CLNP> Deleted the DriverPacks, which were located in "C:\D".
2009-12-07 16:50:51 : <CLNP> Deleted "C:\hwids.dat"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\DPsFnshr.ini"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\devcon.exe"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\makePNF.exe"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\pmtimer.exe"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\DSPdsblr.exe"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\mute.exe"!
2009-12-07 16:50:51 : <CLNP> Deleted "C:\DriverPack_*.ini"!
2009-12-07 16:50:51 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2009-12-07 16:50:51 : Program terminated.

Looks like it worked just fine...

did you reboot so in use files could be deleted too, (like the finisher itself)
- it is very important you reboot before checking! -

Did you verify the problem still exists when using DriverPacks BASE 8.12.5?

that is the release candidate... it is preferred to the latest nightly

technically you have to be on the testing team to get support for nightlys.
The reason is if you are not on the testing team you cant read the related posts that go with the latest nightly.
Therefore you don't know what we are testing, or what the known issues are, or even what we changed or why.
Not that we are much on rules . the nightly server is not some big secret However, the Testing Team Forum is hidden from the public. It's just risky and definitely for non production machines - Testing Only. It's always better to go with RC (Release Candidates) or finals.
If the nightly were any good then we would make them release candidates - Please consider this for a moment...
The fact that they are nightly means they are either known to be broken, or assumed to be broken !

It's better because it is almost a final release... much much better !

It's better for us too, that way we know what to put in the next nightly.
If you find an issue we will invite you to try a specific nightly... one to address your issue
The best way to do it is to only use a nightly if you are invited to do so... Or if someone with a similar issue to yours is invited to try a specific nightly, and you tested that pack and reported back to that thread !
(sometimes when we fix one we break another... its just to much of a risk if you don't know what the nightly is for, or who submitted it - perhaps it's a potential DriverPacks NT5 Packs Team, newbie's first crack at a nightly LOL).

We are not boneheads either many times the nightly are just fine, but why risk it?
We Know for a Fact the Released ones are ROCK SOLID!
and RC Versions are tested thousands of times and believed to be just as solid .

IE It's a no brainer if you are having issues with a nightly... We already know they are broken
( IDK why people think you can just drop some files in a pack and it's done... OMG... We wish!!! )

Have a great day, and thanks for your help - Reporting makes you part of the team too!

I added code tags for you
- you can edit your post to see how i did that, it helps keep the thread from getting too long on any one page .

I suspect that the finisher call, is not...  DPsFnshr.log wil be in %systemroot% (\Windows\DPsFnshr.log ?)
IF not then we know that your guirunonce call to the DriverPacks Finisher is failing

Are you editing the WinNT.sif (or anything else) after you slipstream the DriverPacks?

Are you using DriverPacks? What was /is the basic outline of your process to create your source?
What versions... are you slipstreaming win 2k? win xp? win 2k3? what Service pack? did you slipstream that SP with nLite? did you remove anything with nLite. Did you integrate any updates or hotfixes. Use RVMI or other updater w/ packages. What version of nLite? What version of DriverPacks BASE, DriverPacks used? and their versions? HWIDs? was DriverPacks the last step in your process? Are you installing from ODD? did you use M1 or M2? did you include any 3rd party DriverPack? Why have you not attached any logs? Both the DPs_BASE.log AND DPsFnshr.log are required for this... and will answer a few of the above questions.

Did you reboot the machine after the install and before you checked for \D\? (files can't be deleted when in use )
How was the finisher called? did you use KTD?

Help us to help you... Details are the key.

[url=TinyURL.com/pqum87c]Read BEFORE you post.[/url] - Link in my signature

Examples given here...
Posting guidelines and forum rules.

The search path used to find drivers is stored as a registry entry.
Unfortunately the path length (with all main and all 3rd party DriverPack) has reached the limit of a single registry entry in Win XP. (approximately 1 MB)

The work around is not to include too many packs at once, All of the main packs and a handful of 3rd party DriverPack works.
If you attempt to include them all you will exceed the 1 MB limit.

I have been trying to get everyone who contributes to be aware of this... Especially in the 3rd party DriverPack.

Many of the 3rd party DriverPack have huge path structures delete one or two packs of your choice and BAM it's fixed...
I would get rid of 3rd party DriverPack, not a main pack like graphics

One fix has been to use SAD to install the Third Party DriverPacks from guirunonce or runonceex.

thanks for reporting and welcome to DriverPacks!

BASE 8.12.5 is newer than 9.02.0.1...
9.02.0.1 was an experiment in SysPrep that was abandoned... I should probably just delete it.

8.12.5 = fifth update to to 8.12 code
9.02.0.1 = Alpha / Beta - not released to public, not ever updated (.1), only supported for testing team (before it was abandoned).

BASE 8.12.5 was updated in June (making it technically 9.06.00 BUT since the upates were quite minor i elected to make 8.12.4 ~ 8.12.5 instead of a full revision#)

If you are not SPECIFICALY doing SYSPREP then don't even fool with 9.02
It has known bugs, and it's missing updates, that were only fixed in the 8.12.x series / branches of the code.

Again, the 9.02.0.1 (an attempt at sysprep) was abandoned...
mostly because Galapos Offline SysPrep works flawlessly.
No sense in reinventing the wheel .

They are quite active over there...

I am subscibed to all the Hardware forums at ubcd4win
They just released an update about a month ago and are getting ready for another release...
I know this because i am going to have to unlock the sound drivers for the new release... (shhhh! its a secret)

jeff

Because the included drivers have not been updated for years... and probably are not going to be ever updated again

If they are updated it will be available as a MS update  
That is to say that they are not outdated, just old.

look at it this way... if we add them to the packs they STILL take up just as much room on the cd...

Most of us gave up on CD's years ago... dvd or usb! 
If you have a computer so old it only has a cd you have three really good options...
1) install a DVD burner they are only 20 dollars and an upgrade to the customer and a $ervice for you.
2) hang a DVD burner they are only 20 dollars - you do have an extra one don't you.
3) install from USB DVD, or other USB device.

the usb boot setup was developed tested and initialy released at 911... years ago.   - I'd start there - also check with our good freinds at UBCD4Win perhaps an "all in one thumb" is in your future ??? 
[ No, I did not say you were all thumbs! ]

there are lots of copy cats   MS even

if you legitimately obtain win7 as a download, you have an option to choose USB storage as install media