Topic: devPath.EXE problem

WinXPProSP1, no visual output when devPath.EXE runs yet disk activity.

After 1st user login DevicePath contains:

%SystemRoot%\Inf;C:\WINDOWS\system32\1025;C:\WINDOWS\system32\1028;C:\WINDOWS\system32\1031;C:\WINDOWS\system32\1033;C:\WINDOWS\system32\1037.........

When devicePath is run ( after install )

like this devPath.EXE "C:\D" currentDir is enumerated !
like this devPath.EXE  C:\D  seems to work ( but still not in preSetup ).

Replaced devPath.EXE in preSetup.CMD with:

@echo off &title %~n0 &color 0B &setlocal enableExtensions enableDelayedExpansion

...

set "devicePath=%%systemRoot%%\Inf" &for /d /r "%systemDrive%\D\" %%? in (

    "*"

) do     set "devicePath=!devicePath!;%%~?" &(echo(%%~?)
::
if "!devicePath:~8097,1!" neq "" (
    ::
    echo.DevicePath maximumlength exceeded.
    goto :error ()
)
set "devicePath=!devicePath:~0,8097!"
reg.EXE add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion" /t REG_EXPAND_SZ /v "DevicePath" /d "!devicePath!" /f ||goto :error ()


Any ideas ?
Thanks,

Re: devPath.EXE problem

any Ideas about what? You did not state any question, nor specific issue.

Please post your DPs_BASE.log

also please read "Read BEFORE you post" linked in my signature.
*you also agreed that you read this when you signed up.

The search feature is also very useful.

Please also note that "Stickied" Topics can be quite useful...
Like this one in this subforum directly above your topic.
http://forum.driverpacks.net/viewtopic.php?id=5081

IN Addition there is this post in the FAQ section of our site
http://forum.driverpacks.net/viewtopic.php?id=4446

We have been around almost ten years ... ALMOST ANY question you may have is already addressed here somewhere big_smile.

PS Devpath is not meant to be run after the install.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

The drivers are not installed, I suspect devPath.EXE.
Is it normal that devPath.EXE doesn't produce output ?
I remember it would say something like:
enumerating C:\D....
but it doesn't, yet there is disk activity while devPath.EXE runs.

After logon I check HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath and then it contains anything but C:\D subfolders. It contains what looks like the systemRoot subfolders.

ps:
How to install the Nvidea/ATI icon in the startMenu after windows setup ?
Then I would install those packs after windows has been installed...

Dps_BASE.log
2013-05-11 21:39:40 : <INIT> DriverPacks BASE 10.06 initialized.
2013-05-11 21:39:40 : <INIT> Host environment: WIN_XP Service Pack 3 X86 on a X64 CPU.
2013-05-11 21:39:40 : <INIT> Created temporary working directory.
2013-05-11 21:39:40 : <INIT> Imported proxy settings from Internet Explorer.
2013-05-11 21:39:40 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack Graphics A 1206!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack Graphics B 1206!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack Graphics C 1206!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack LAN 1205!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack Mass Storage 1209!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack Sound A 1111!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack Sound B 1111!
2013-05-11 21:39:40 : <INIT> 	Detected DriverPack WLAN 1202!
2013-05-11 21:39:40 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2013-05-11 21:39:40 : <INIT> 	Finished scanning.
2013-05-11 21:39:40 : <INIT> Using settings file in custom location: C:\DPs_BASE_1006\ED_DPs_BASE.INI.
2013-05-11 21:39:40 : <INIT> Detected settings file "C:\DPs_BASE_1006\ED_DPs_BASE.INI".
2013-05-11 21:39:40 : <INIT> Windows XP Professional -  SP1 detected.
2013-05-11 21:39:40 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2013-05-11 21:39:40 : <INIT> Imported settings from settings file.
2013-05-11 21:39:40 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2013-05-11 21:39:41 : <PREP> Removed all attributes from \I386.
2013-05-11 21:39:41 : <PREP> \I386\winnt.org was not found, \I386\winnt.sif was not restored.
2013-05-11 21:39:41 : <PREP> Either txtsetup.org or dosnet.org was not found. The removal of 
2013-05-11 21:39:41 : <PREP> any Service Packs we may have added with Driverpacks and or 
2013-05-11 21:39:41 : <PREP> the removal of any Mass Storage textmode drivers was skipped
2013-05-11 21:39:41 : <PREP> Deleted \I386\presetup.cmd.
2013-05-11 21:39:41 : <PREP> Replaced original setup: method 2 was used previously.
2013-05-11 21:39:42 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.
2013-05-11 21:39:42 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2013-05-11 21:39:42 : <SLIP> C:\DPs_BASE_1006\QSC\wnt5_x86-32_uni_DP_MassStorage_1209_textmode\DriverPack_MassStorage_wnt5_x86-32.ini
2013-05-11 21:39:44 : <SLIP> Processing Mass Storage files now. This may take a minute.
2013-05-11 21:39:47 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2013-05-11 21:39:47 : <SLIP> txtsetup.sif Backed-up Successfully
2013-05-11 21:39:47 : <SLIP> dosnet.inf Backed-up Successfully
2013-05-11 21:40:01 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2013-05-11 21:40:04 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2013-05-11 21:41:31 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2013-05-11 21:41:31 : <SLIP> Created necessary directory structure for method 2.
2013-05-11 21:41:31 : <SLIP> Copying files necessary for method 2.
2013-05-11 21:41:32 : <SLIP> Extracted additional files necessary for method 2.
2013-05-11 21:41:32 : <SLIP> expanded setup.ex_ to setuporg.exe
2013-05-11 21:41:32 : <SLIP> SETUP.EX_ Backed-up Successfully
2013-05-11 21:41:32 : <SLIP> Compressed setup.exe to SETUP.EX_.
2013-05-11 21:41:32 : <SLIP> Method 2 setup.ex_ installed
2013-05-11 21:41:32 : <SLIP> Created \I386\presetup.cmd file.
2013-05-11 21:41:32 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2013-05-11 21:41:32 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2013-05-11 21:41:35 : <SLIP> Copied DriverPack Graphics A to \OEM.
2013-05-11 21:41:39 : <SLIP> Copied DriverPack Graphics B to \OEM.
2013-05-11 21:41:41 : <SLIP> Copied DriverPack Graphics C to \OEM.
2013-05-11 21:41:41 : <SLIP> Copied DriverPack LAN to \OEM.
2013-05-11 21:41:44 : <SLIP> Copied DriverPack Sound A to \OEM.
2013-05-11 21:41:47 : <SLIP> Copied DriverPack Sound B to \OEM.
2013-05-11 21:41:47 : <SLIP> Copied DriverPack WLAN to \OEM.
2013-05-11 21:41:47 : <SLIP> Copied DriverPacks to \OEM.
2013-05-11 21:41:47 : <SLIP> svcpack.in_ Backed-up Successfully
2013-05-11 21:41:47 : <SLIP> Extracted svcpack.inf and deleted svcpack.in_.
2013-05-11 21:41:47 : <SLIP> uni2ansi.exe of svcpack.inf was successful
2013-05-11 21:41:48 : <SLIP> Updated \I386\svcpack.inf file to support KB888111.
2013-05-11 21:41:50 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2013-05-11 21:41:52 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2013-05-11 21:41:52 : <SLIP> KB883667 will not be added to Windows XP Professional -  SP1
2013-05-11 21:41:53 : <SLIP> SVCPACK.INF was CAB compressed to SVCPACK.IN_
2013-05-11 21:41:53 : <SLIP> WINNT.SIF Backed-up Successfully
2013-05-11 21:41:53 : <SLIP> Updated \I386\winnt.sif to support method 2.
2013-05-11 21:41:53 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2013-05-11 21:41:53 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2013-05-11 21:41:53 : <SLIP> DP_Install_Tool was copied successfully
2013-05-11 21:41:53 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]

; preferred language
prefLang	= "English"

; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"

; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "no"


[Settings]

; disc/bartpe/multibootDisc
instPlatform	= "disc"

; trailing backslash is allowed, but not necessary
location	= "C:\DPs_BASE_1006\OUT"

; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"

; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"

; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


[OptionalSettings]

; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"

; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"

; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "yes"

[SelectDriverPacks]
DP_Chipset 		= "yes"
DP_CPU				= "yes"
DP_Graphics_A	= "yes"
DP_Graphics_B	= "yes"
DP_Graphics_C	= "yes"
DP_LAN				= "yes"
DP_MassStorage	= "no"
DP_Sound_A		= "yes"
DP_Sound_B		= "yes"
DP_WLAN			= "yes"
DP_MassStorage_textmode = "yes"

[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"

2013-05-11 21:41:53 : <CLNP> Create a DPs_Base.log backup @ C:\DPs_BASE_1006\LogFiles\DPs_BASE_13-05-11_21-41.log
2013-05-11 21:41:53 : <CLNP> Program terminated.

Last edited by ikbeneenlul (2013-05-12 07:57:19)

Re: devPath.EXE problem

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

you would need to check to see if they are there before the computer reboots to the GUI.
(or disable the finisher)

There isn't a reason that this should fail for you except that the BASE log indicates that your source is not totally clean.

Please try again with a "Clean" source. (Read - fresh copy of original hologramed Microsoft disc)
Additionally most of us slipstream SP3 into our install... but that is not mandatory.

Jeff

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

OverFlow wrote:

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.

OverFlow wrote:

(Read - fresh copy of original hologramed Microsoft disc)

Sorry, where do I read that ?

OverFlow wrote:

Please try again with a "Clean" source.

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 ?

OverFlow wrote:

Additionally most of us slipstream SP3 into our install...

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

Last edited by ikbeneenlul (2013-05-12 11:14:55)

Re: devPath.EXE problem

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

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.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

ikbeneenlul wrote:

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

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

2013-05-11 21:39:41 : <PREP> Replaced original setup: method 2 was used previously.
2013-05-11 21:39:42 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.

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

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: devPath.EXE problem

OverFlow wrote:

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....

mr_smartepants wrote:

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

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


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.

Last edited by ikbeneenlul (2013-05-12 23:55:15)

Re: devPath.EXE problem

the taskbar icons are part of the driver... a properly installed driver accomplishes this. It is not something we or BASE does.

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 wink. 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 big_smile.

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.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

Can we agree the only thing devPath.EXE does is adding all subfolders to the DevPath regKey ?
In that case I'll just do it manually using these batch commands.

OverFlow wrote:

the taskbar icons are part of the driver... a properly installed driver accomplishes this. It is not something we or BASE does.

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...

OverFlow wrote:

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 wink. 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 big_smile.

Better is the enemy of good wink

OverFlow wrote:

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.

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

Last edited by ikbeneenlul (2013-05-13 05:04:08)

Re: devPath.EXE problem

ikbeneenlul wrote:

"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.

OverFlow wrote:

... "people throw away far better equipment than this"

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.

ikbeneenlul wrote:

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

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

"               Minimum
Processor     233 MHz[1]
Memory     64 MB of RAM[2]

    ^1 Even though this is Microsoft's stated minimum processor speed for Windows XP, it is possible to install and run the operating system on early IA-32 processors such as a P5 Pentium without MMX instructions. Windows XP is not compatible with processors older than Pentium (such as 486) because it requires CMPXCHG8B instructions.[94]
    ^2 A Microsoft TechNet paper from Summer 2001 (before Windows XP's actual release), states that: "A computer with 64 MB of RAM will have sufficient resources to run Windows XP and a few applications with moderate memory requirements." (Emphasis added.) These were said to be office productivity applications, e-mail programs, and web browsers (of the time). With such a configuration, user interface enhancements and fast user switching are turned off by default.
    For comparable workloads, 64 MB of RAM was then regarded as providing an equal or better user experience on Windows XP with similar settings than it would with Windows ME on the same hardware. In a later section of the paper, superior performance over Windows ME was noted with 128 MB of RAM or more, and with computers that exceed the minimum hardware requirements.[95]
      Quoted from:  http://en.wikipedia.org/wiki/Windows_XP … quirements
       additional reference:  http://support.gateway.com/s/software/m … u136.shtml
"

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?

Last edited by TechDud (2013-05-13 11:32:56)

Re: devPath.EXE problem

http://support.microsoft.com/kb/314865
Windows XP minimum requirments.
Pentium 233-megahertz (MHz) processor or faster (300 MHz is recommended)
At least 64 megabytes (MB) of RAM (128 MB is recommended)

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 big_smile.

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 tongue
- 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.) sad.  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)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

TechDud wrote:

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.

OverFlow wrote:

Devpath may be failing due to insufficient ram.

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.

OverFlow wrote:

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.

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 smile

Last edited by ikbeneenlul (2013-05-13 13:18:41)

Re: devPath.EXE problem

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

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

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

That's not your fault, OverFlow.  I know that you are being sarcastic.

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

ikbeneenlul wrote:

"I did not read the forum rules and guidelines"

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

ikbeneenlul wrote:

... "because fewer systems seem to accept SP3"

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.  smile

Last edited by TechDud (2013-05-13 16:31:03)

Re: devPath.EXE problem

OverFlow wrote:

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 tongue

TechDud wrote:
ikbeneenlul wrote:

... "because fewer systems seem to accept SP3"

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.

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 wink

TechDud wrote:

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.

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

Last edited by ikbeneenlul (2013-05-16 14:04:50)

Re: devPath.EXE problem

the question remains, millions of other users have no issues.

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.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: devPath.EXE problem

That's what I thought, either millions of other people have the same issue or the cause is my source. Since millions of others have no issue, the problem must be my source.

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.

Last edited by ikbeneenlul (2013-05-18 10:41:09)

Re: devPath.EXE problem

I would gladly provide it to you if i had it... it was written and supplied to us by a third party. (Pyron i belive)


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.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.