Please submit the update to the bugtracker either the current translator will pick it up or i will - Thanks for the offer and the kind words

Jeff

PS can you test the nightly? (do you still have the notebook?)

We' ll do!

PS: Argh, I dont have the notebook anymore, it was from a client (I am a computer tech).

Jeff

PS can you test the nightly? (do you still have the notebook?)

haven't had a chance yet... normally JakeLD does Mass and he has been too busy... I only did mass last time to fix a bug that was reported in DriverPacks BASE. It was neccessary to correct a flaw in mass to achieve the fix.... Since most people can update mass and only I can update DriverPacks BASE i try to spend my limited amount of free time on the DriverPacks BASE code.

There is a nightly version of chipset up... sometimes conflicts in chipset will affect mass storage especially with those POS nvidia MB drivers.

Hey no problem, just checking!
Just wondered if it was beeing checked, since this problem should probably be posted in another section.

I guess you can close this topic, since everything was solved, and I already managed to get the vaio notebook runing with the old DriverPacks BASE.

Thank you so much for the attention and congrats on the project!
KEEP IT UP!!

BTW, there has been a problem with the portuguese(brasil) translation to the DriverPacks base for a while now, If you want it, I can do the translations from now on, or maybe just correct the flaw.

If you need anything, count on me!

There is a nightly version of chipset up... sometimes conflicts in chipset will affect mass storage especially with those POS nvidia MB drivers.

there is a maximum size that can be passed to the DevPath registry entry... Depending on who you believe it is either 16k or 64k... if you add enough packs then you will exceed the limit... so it is not a question of which one but rather which ones in combination will pass the limit.

I recommend you use SAD for the 3rd party DriverPack.
Simply create a SAD folder with only the 3rd party DriverPack
(language and run-times should be included with the main slipstream, if you need them).
Call DP_Inst_tool.cmd to install your tpdps
I recommend doing this after the finisher runs for the main packs, but you don't have to.
If you don't call the DP_Inst_Tool after the finisher runs then all the main packs will be checked against the system a second time . this would be time consuming and redundant. no harm done just a waste of time .

@m0scha try slipstreaming again this time eliminate all 3rd party DriverPack except graphics languages, graphics Physx, and runtimes. PS if you are installing .net with an update package (like sereby's) then DO NOT include the runtime 3rd party DriverPack.

Hi OverFlow,
sorry for reporting lately (my external DVD-Drive was blown up and i had to get a new one...)

Yes I'm using Serebys Updatepack ;-)
- Removing DP_Runtimes allone didn't work, but after removing all my 3rd-Party Driverpacks it's working.

Would be interesting which 3rd Party DP is causing the Problem:

I used these before:
- DP_Runtimes_wnt5_x86-32_912.7z
- DP_Graphics_Languages_wnt5_x86-32_1003.7z
- DP_Graphics_PhysX_wnt5_x86-32_912.7z
- DP_Misc_wnt5_x86-32_90909.7z
- DP_Modem_wnt5_x86-32_100101.7z
- DP_TV_wnt5_x86-32_90915.7z
- DP_WebCam_wnt5_x86-32_100104.7z

I just noticed that the old build works, but there is an exclamation point next to the controller.

But I noticed something,
I installed on a 40gb drive and it worked.
When I tried a 250gb drive I got this problem.

Maybe a sata1/sata2 issue ?

1- Old desktop PC
2- Sony Vaio not so new

On 1, the installation worked perfectly.
On 2, installation goes well until the first time windows stars. Then I get a BSOD 0x0000007B. Cant go into safe mode, nothing.

Seems like a problem with the hdd controller.
I tried my old driverpack build, and it worked like a charm.

Sorry it took me long to respond, but I only have spare time on the weekend and this weekend was crazy.

@m0scha try slipstreaming again this time eliminate all 3rd party DriverPack except graphics languages, graphics Physx, and runtimes. PS if you are installing .net with an update package (like sereby's) then DO NOT include the runtime 3rd party DriverPack.

Thx OverFlow,

this could be the Reason (I'm using Serebys Updatepackt & 3rd Party Driverpacks).
I'll remove the 3rd Party Driverpacks, make another Testdrive and reporting back if this was the reason.

I always keep a spare DVD around and a USB to SATA/IDE cable around - will the laptop boot from USB?

It does, but I had a feeling the HD was bad, so I used seatools to check it (its toshiba but I dont know any toshiba software) and guess what ?

Smart has been triped
and after formating still 1 error detected.

As Im writing this, I did exactly how you instructed me.

Created a copy of my xp install named xpsp3-nlite
used nlite on it to add all updates and copied winnt.sif and $oem$ to it

created a copy of that folder named xpsp3-nlite-driverpack
and ran dpbase on it
checked the log and all driverpacks and binaries were copied to oem folder of my install path

Now I will run nlite again to create the iso and finally burn with nero.

To use it on a 100% working desktop.

Ok, just tried the iso on a virtual machine and the drivers were extracted, so Im gonna burn to a dvd-r to install on the desktop.