1 Topic by ikbeneenlul

(1 replies, posted in Feedback and Support - DriverPacks Base)

I need to integrate qChain.EXE into svcpack.IN_.

; QChain.exe gives system administrators the ability to safely chain hotfixes together.
; Hotfix chaining involves installing multiple hotfixes without rebooting between each installation.
; Without this tool, the only supported method is to reboot after each hotfix installation.
;
; The QChain.exe tool has the following benefits:
;    It increases uptime for servers because computers are not being rebooted between each hotfix installation.
;    It allows faster installations of multiple hotfixes on a single computer.
;    It is a solution that works on both Windows 2000 and Windows NT 4.0.
;
; Chaining Hotfix Installations Without QChain.exe Is Not Safe

There are 3 hotfixes in the 'bin\wnt5_x86-32' folder;
KB883667.7z, KB888111.7z, KB921401.7z

If I expand svcPack.IN_ I see

[Version]
Signature="$Windows NT$"

[SetupData]
CatalogSubDir="i386\hotfixes"

[ProductCatalogsToInstall]

[SetupHotfixesToRun]

I was suprised to see they weren't mentioned here. Also the folder i386\hotfixes doesn't exist.

I did locate newdev_SP1.dll which is inside KB883667.7z  inside the I386 folder, but couldn't find it's accompanying KB883667.CAT file.

But then how were they integrated ? Were they slipstreamed ? Can a hotfix be slipstreamed ?

And won't that be a problem as my memory is hazy, but if I remember well Microsoft said qChain.EXE had to be applied before any other hotfixes.


Thanks

Go to forum: Feedback and Support - DriverPacks Base

2 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

3 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

4 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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

Go to forum: Feedback and Support - DriverPacks Base

5 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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 )

Go to forum: Feedback and Support - DriverPacks Base

6 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

7 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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

Go to forum: Feedback and Support - DriverPacks Base

8 Reply by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

9 Topic by ikbeneenlul

(18 replies, posted in Feedback and Support - DriverPacks Base)

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,

Go to forum: Feedback and Support - DriverPacks Base