Try it with an unaltered source, does the issue disappear?
re-add your changes one at a time until the issue reappears.
you must be deleting a file that is a dependency, or otherwise damaging the functionality.

still waiting on Read BEFORE you post. I will lock this thread if you do not comply with  Read BEFORE you post. #6
If i can duplicate your issue i can solve it... it's that simple

I have been very patient with trying to help you. You have done everything but flip me off for my efforts.
I'm getting tired of it. Help us to help you, or be gone.

Maybe I'm able to pinpoint the problem. Am I allowed to see the source code of devPath.EXE ?
If relevant, I'll report my findings.

I did not say that the only possable cause was your source, I belived based on your input (what very little there is of it) your source seems most likely. It still does. It will remain so until further info (many times requested now) is provided.

What do you do differently than all others?

you have still failed to complete "Read BEFORE you post".

Comply or be labeled a troll.

PS you state your source works flawlessly... (you did NOT state it is original and unchanged)
if that is the case then why are you here?
You have done something that no one else does.

if it fails on multiple platforms then the issue must be your source.

you also failed to mention that previously, entirely my fault.

All the other million programs seem to run just fine. Just this program fails to work properly. It seems to make an assumption that isn't valid so the problem must be my source. Assumption is the mother of all f*ck-ups

A slipstreamed installation of one servicePack that installs fine and a slipstreamed installation of another servicePack that fails does not indicate a hardware problem. Certainly when the program displays an error message, the system operates fine otherwise and runs the servicePack if installed later on. A faulty unit can be excluded, the system passes every stress-test. CD/DVD can be excluded, same happens with a networked installation. update packs i include can be excluded. I am talking about an original disc that has been slipstreamed with servicePacks. My source can be excluded too, it is original and tested with many systems succesfully.
Don't blame the machine, mistakes are human

My source image is verified with it's checksum before extraction.

It sure does help to not waste our time when critical information is included.
We are volunteers, not profiteers.

Give it a go.  Even i have to re-read the rules, once in a while.

I have yet to see an ATAPI Setup with at least a P-II or Athlon & 256MB that could not fully Setup Windows from my own slipstreamed XP SP3 disc, other than faulty units.  I have seen exceptions to that, yet those had issues with a CD/DVD drive (sometimes specific models) being on the same controller, or simply reading a scratched disc or poorly-supported media.
When i have encountered Setups that could not complete, or spat out errors, there was either a problem with the update packs i include with RVMi, my source, or a genuine hardware issue (not considering DP's development).  This includes the AMD chips that were an original issue with SP3.

I consider XP-SP3 Setup to be a genuine hardware test, other than for the newest and where NT5 drivers do not exist, or the oldest where memory limits patience.

At any rate i deduce from your comments regarding 4MB that you are likely using nLite.  This can corrupt one's source.  Remember that if you have copied your disc to a folder, you have copied it onto R/W hardware.  It can and will be changed eventually, if you do not monitor changes to that folder &/or refresh it's contents.  This has been noted and repeated on occasion elsewhere in this forum.

Oh, yes.  I would replace the coin-cell in any that show those infamous crystalline residual signs of leakage for any vintage to antique computing hardware. 

you also failed to mention that previously, entirely my fault.

That doesn't seem accurate, so here's some info from Wikipedia:

Few years back there was a competition on some site ( which I obviously don't recall ) where people challenged each other to get XP on a machine as low as possible. Some dude claimed he installed XP on an i386. I was lucky to be able to test that out on an i386sx and he was right. I tried to go under 4MB of ram but that gave some error about insufficient memory during guiSetup.

I am not testing it on that Pentium1, was just explaining I don't slipstream SP3 because fewer systems seem to accept SP3. I tested on a PIII, PIV and VMware.

I did not read the forum rules and guidelines but I did check the FAQ forum and the search function. I posted the DPs_BASE.log. The HWID's are not relevant ( the DevPath issue also happens in VMWare ).

Let's say it worked once. Then I downloaded the new dpsBase 10.06 and some more and new driverpacks. When I installed this on a computer I noticed the drivers were not installed. So I installed it on another computer with the same result. Then I knew something was wrong because both pc's used some drivers from the driverPacks in the past. I figured out the devPath issue using VMWare.

I may never find out what the issue is/was using devPath.EXE.
It works using batch to set the DevPath.
I shall not waste our time further.

Kind regards, and thanks for the info

so your processor fails minimum requirements and your ram is at the bare minimum.
this machine is built for windows 95, please expect problems with windows NT5 OS's.

Devpath may be failing due to insufficient ram.

I am going to repeat myself, again... Try SAD .

the .INS tag files simply tell the finisher which driver install you prefer to run.
ATI or Nvidia and the old or new version.
the tag files are simply dummy files we create to pass your selection during install to the finisher
Nvidia and ATI supply the drivers, we just run them based on your selection and the card found.
these tag files are found in the root of the drive. not a line in an INF file.
we don't do anything to make those icons.
Like i said before those icons are installed by the driver. Install the driver, and there they are...

Since you failed to provide the requested info

I asked you twice - and you agreed to provide it without our asking when you signed up
- "Read BEFORE you post"
how many of the seven listed items have you checked off as done?
Half of one out of seven I think (half of number 5) that is about 7% of what we require.

If you don't provide requested info then i (we) can't help.
You gave me 7% of the info i need to help and i gave you 10% of your answer
here we are 12 posts later still waiting on info that should have been in your first post.

i could have given you 90 percent of the answer on my first post if you would have done as requested.

GIGO

ps http://support.microsoft.com/kb/138349
Windows 95 Installation Requirements
Personal computer with a 386DX or higher processor (486 recommended)
4 megabytes (MB) of memory (8 MB recommended)

You quoted the minumum requirments for windows 95... LOL
But you're not installing win 95 R U? ROFL
and I have to agree this machine would ROCK windows 95, try that and see how it works
- or did you think you were installing win 95???

can you remove a screw with a claw hammer?  Sure.
Is it a good idea.  No.

PSS JUST TO KEEP HAMMERING AWAY AT THIS. WHAT VIDEO CARD IS INSTALLED?
(HAD YOU PROVIDED THE SECOND HALF OF #5 IN READ BEFORE YOU POST I WOULD KNOW THIS ANSWER ALREADY. (i refer to the HWID's in case you are unsure.) .  THIS IS STARTING TO GET ANNOYING. It clearly says in red Always Required

in your next post number 1 through 7 and then tell us if you have provided that info or completed the task at the time of your FIRST post. All items that you must indicate as negative (which is all seven), Please now provide the missing info or indicate you have now completed the item. (this includes the title of your thread)

"In the old days, machines were not build to be replaced, they were build to last

I agree.  In addition, some components used real gold, not the alloys used as of late which are more prone to oxidization and bi-metallic corrosion.  (I would have to double-check my half-cell electrochemical tables to confirm that last part concerning "bi-metallic corrosion"; call it an observation, not necessarily fact.)  Also, they used leaded solder, which is not as prone to thermal, whiskering or other inclusive phenomenon as the early and or inexpensive unleaded crap.

I rely upon this fact.  Often it is only a lack of cleanliness, or blown capacitors in a P/S (stored charge in such can kill; beware), that prevent stable operation.

If only you could plunk an AMD K6-2/500 & another 64MB or so in there.  Although as OverFlow hinted, those CPU's performed better with a 16-bit OS.

That doesn't seem accurate, so here's some info from Wikipedia:

There you have it.  Although that processor doesn't appear to meet minimum speed requirements (effecting timing in some cases?), it can "work", yet with that, yet with a minimum of memory some features will be disabled.  Does that effect DEVPATH?  OverFlow would know better than me.  I thought some of this info would be relevant and/or helpful.

As a parting thought, an Apple I motherboard (no case) recently sold at auction in December for $640,000!
     http://appleinsider.com/articles/12/12/ … an-auction
       & http://www.zdnet.com/apple-i-to-be-sold … 000015200/
   That "Pascaline" seems to have that "steampunk" look, yet it would seem that an abacus would be more "user-friendly"!

Just because it is a "dinosaur" doesn't necessarily mean that it is worthless.  After all, those that ignore history are oft doomed to repeat it or at least "rhyme" with it.

  I do admire your courage and patience in working on this vintage hardware.
edit:  post a small image or two, or link to downloadable pic, to show off hardware that endures.  What brand is that?

This is confusing, I can install the video drivers after windows has been setup, but then I don't get those ATI/NVidea icons in the taskbar.

[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming Graphics DriverPack)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl        = "CCP"
Nvidia_cpl    = "1"

Description:
The selections above will only be applied by the PriverPacks.net finisher if an appropriate graphics card is found in the target machine.

So I look inside DPsFnshr.ini but I see no related settings.

I wonder what "ATICCP.ins" and "Nvidia.ins" are for...

Better is the enemy of good

My P1 has 64MB of ram ( I verified XP requires an i386 with 4MB of ram or better )

really... you are connecting this to a server, is the server also a dinosaur? I understand as well as anyone not having the money to buy new PC's but people throw away far better equipment than this . I do have a P1 class system in my inventory, and a 486, but i don't try to run NT5 OS's on them .

How much ram is in this machine?
SAD / DP_Install_Tool.cmd you should be able to install LAN drivers (*all drivers really) after the install.

i think it's dirty because the log says it needed cleaned up.

I must have run dpsBase twice on the same source.
I think it happened because I manually tested because of the drivers problem...
I suspect it won't make any difference but I'll do some more testing....

In the old days, machines were not build to be replaced, they were build to last

The only pack that I really need to be installed is the LAN pack, so the client can connect back to the server after windows has been installed.
Does anyone know if it's possible, how one could install the video driver's quickmenu icons in the taskbar after windows has been installed ? This is the main reason why I do that through driversBase. I just have no clue how dpsBase does this.

If I use SP0, SP2 or SP3 then guiSetup crashes on my Pentium1 90Mhz

I haven't even SEEN a Pentium 1 in over 10 years!  Get some new(er) hardware!

Yup, source is suspect if DriverPacks BASE is already detecting a prior (broken) method-2 integration.

it may have come from a clean source at one time but it was not clean when you ran BASE on it.
all sources are clean when copied from a valid disc. once copied from the original read only media they may or may not be clean any more. If you do this copy yourself then you know exactly where you are starting from.

again...
Start with a clean copy from a MS hologramed disc.  I notice you did not say that is what you did.
you said "As far as I know, my source is an original Windows XP Professional disc/iso file."
That means your source is suspect.

If you start with a known clean source then i think you will no longer have an issue.

Let's put it this way millions of other users do this with no problem....
what is different with your situation? The source for one...
One problem identified. start there.

the entries are removed from the registry before you are presented the desktop. The the DriverPacks Finisher does this automatically.

Forgot to mention, the finisher didn't run yet, I disabled that for testing...
I see entries, all subDirs of systemRoot.

Sorry, where do I read that ?

As far as I know, my source is an original Windows XP Professional disc/iso file.
It gets extracted from the image and is then slipstreamed with SP1.

Why you think it is dirty ?

If I use SP0, SP2 or SP3 then guiSetup crashes on my Pentium1 90Mhz