(4 replies, posted in Software)

I used to rely on hidec for silent WinRAR installers, but have since moved to Oleg Scherbakov's modified 7zip stub.  It has built in support for silently executing batch scripts.

However I do still find uses for hidec and it drives me crazy when other people complain about AV warnings in my stuff.


(4 replies, posted in Software)

Hidec is widely used to silently run batch files or other console programs.  One of it's virtues was the fact that it wasn't picked up by antivirus like cmdow is.  Unfortunately that has changed and it's now picked up by a few scanners.

Here is what VirusTotal says about it:

AntiVir - SPR/Tool.Hide.A
AVG - HideExec.EV
Webwasher-Gateway - Riskware.Tool.Hide.A

I've removed these signatures.  File size is still the same at 1.5kb, I did not pack the exe.  Please keep this file here... don't spread it around everywhere.

Usage: hidec /w program
/w is optional and instructs Hidec to wait for program termination

password: driverpacks.net

updated, created a complete guide.  would a kind mod please clean up my useless posts for me?

If you've ever tried to debug a failed installation with the recovery console, you've probably run into the issue of your password not being accepted.

Here's how to get around it:

open spcmdcon.sys with a hex editor.
here's the search and replace bytes:

change  0F 95 85 E3 FD FF FF (setnz [ebp+var_21D])
to:     C6 85 E3 FD FF FF 00 (mov [ebp+var_21D], 0)

and then modifype your patched file and overwrite original.
Now Recovery Console won't ask for password.

Tested on: XP SP3 Recovery Console

If the bytes are different for other versions of windows just let me know and I'll make a patch for them too

I don't use the directory or do anything that would cause it to happen.  The strange thing is it only happens on real hardware.  I can't reproduce it in a VM with the same exact installation image.  Another thing I noticed is that "\D" folder varies in the amount of files successfully deleted.  In one installation it was basically full, in another it only had one folder left.

I have an idea for a workaround, just a simple retry in the AU3 code.  I'll try something out later and see if it works.

this guide assumes you already have slipstreamed driverpacks onto your installation media

part 1: binary edits

1.) copy boot.bin (your 2kb CD boot sector) to boot2.bin
2.) open boot2.bin with hex editor, replace setupldr.bin with myloader.bin
3.) copy setupldr.bin to myloader.bin and open in hex editor
4.) make following changes (for every occurrence):
    setupdd.sys changes to ddsetup.sys, txtsetup.sif to setuptxt.sif, winnt.sif to winnt.org
5.) copy setupdd.sys to ddsetup.sys and open in hex editor
6.) search for unicode string dosnet.inf and change to netdos.inf
7.) use modifype to fix crc in ddsetup.sys and then compress if you want
8.) uncompress setup.org, rename to setp2.exe, compress if you want

part 2: text edits

1.) winnt.org should be fine, but double check that it has what you want
2.) copy dosnet.org to netdos.inf and open in notepad
3.) in [Files] section replace d1,setup.exe with: d1,setp2.exe
4.) in [Files] section add: d1,ddsetup.sys and leave the setupdd entry
5.) copy txtsetup.org to setuptxt.sif and open in notepad
6.) in [SourceDiskFiles] replace setup.exe line with: setp2.exe = 100,,,,,,,2,0,0,setup.exe
7.) in [SourceDiskFiles] add: ddsetup.sys = 100,,,,,,3_,,3,,,1,4

now you're finished, just point your bootloader of choice to boot2.bin for your non driverpacks installation, and of course use your original boot.bin for the driverpacks installation
don't forget to delete bootfix.bin when you make a multiboot disk

hopefully I didn't forget anything...


(10 replies, posted in Software)

maybe before you release it you could implement my bugfix or a similar fix?



Did you overwrite or modify your winnt.sif?  Does it still have the dpsfnshr entry in the guirunonce section?
Do you have any other guirunonce programs?  If so, is there any chance any of them could reboot the system?

I don't think I've ever had a problem with the finisher not running.

post your DPsFnshr.log (@ C:\Windows\DPsFnshr.log) please.

Yeah I hear ya.  That extra time factored into testing a bunch of packs a bunch of times could get old.

Just to clarify though, what I meant by "check once" was a check where say a DP is scanned, and then an entry made in the INI so it isn't checked again later.  But if someone is having problems with corrupt files that probably wouldn't do any good.

I assume by your x2 comment that you would check before and after integration, but probably just a check afterwards would do.  Whatever wink

are you drunk?

I thought the idea of a "check once" sounded good, but really I think if you're having problems with corrupt files that the "check once" won't be much better than a check every time.

I personally don't see the need for it, but it's very simple to implement and could be optional so it might be worth a try.

I did a quick test on this machine (2ghz), and it took 8 seconds to do a  7z.exe t *.7z on LAN/WLAN/Chipset/MassS

Sounds good to me.  Better get started wink

+1 on VirtualBox.  It's the only VM I've been using for the past 6 months.

I used to use only VMWare because it was more compatible and was quite a bit faster than VPC.  But Virtual Box is the best of both worlds:  It's small, fast, and free. (and I haven't had any compatibility issues)

Well, I figured it out.  I installed again and took a look at the runonce key that gets set and it doesn't work.
cmd.exe /c "if exist C:\D  then rd /s /q C:\D"
returns: 'then' is not recognized as an internal or external command, operable program or batch file.

I've updated the autoit script and created a sample DPsFnshr.exe with the changes.

Const $_FINISHERDIR = StringReplace(@ScriptDir, "\", "")

changed to:

If StringRight(@ScriptDir,1)=="\" Then
Const $_FINISHERDIR = StringTrimRight(@ScriptDir,1)
Const $_FINISHERDIR = @ScriptDir


RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce", "retry cleanup of the DriverPacks", "REG_SZ", 'cmd.exe /c "if exist ' & $SET_DPSROOT & "\D  then rd /s /q " & $SET_DPSROOT & '\D"')

changed to:

RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce", "retry cleanup of the DriverPacks", "REG_SZ", 'cmd.exe /c rd /s /q "' & $SET_DPSROOT & '\D"')


RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce", "retry cleanup of the DriverPacks Finisher temp dir", "REG_SZ", 'cmd.exe /c "if exist ' & $_DPSTMP & "  then rd /s /q " & $_DPSTMP & '"')

changed to:

RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce", "retry cleanup of the DriverPacks Finisher temp dir", "REG_SZ", 'cmd.exe /c rd /s /q "' & $_DPSTMP & '"')


forfilled changed to fulfilled ;)

I changed the $_FINISHERDIR constant to what I think the actual intent of the coder was.  The original was kind of a hack and this is more future-proof.

The other two changes produce output similar to this: cmd.exe /c rd /s /q "C:\D"
Tested and working on real hardware.  Directory is no longer left behind.


I don't add/change users with nlite and I haven't modified anything.  It's just a standard point and click DriverPacks integration.  AFAIK I've had this issue with Base for a long time now, but I never really cared enough to report it since it's not that big of a deal.

If exist "%systemroot%\system32\setupold.exe" DEL /F "%systemroot%\system32\setupold.exe"

REM +==========================================================================+
REM |   Finding CD/DVD driveletter.                                            |
REM |--------------------------------------------------------------------------|

REM +==========================================================================+
REM |   Decompressing the DriverPacks to the harddisk - using un7zip.exe.      |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\

REM +==========================================================================+
REM |   Copying/decompressing the files to finish the installation.            |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\

REM +==========================================================================+
REM |   Scanning for driverdirectories.                                        |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\bin\DevPath.exe %SystemDrive%\D

REM +==========================================================================+
REM |   Disable Driver Signing Policy and keep it disabled.                    |
REM |--------------------------------------------------------------------------|
START %SystemDrive%\DSPdsblr.exe


Thanks, but I can read too. I've rebooted no less than 5 times and the directory remains.  Same thing happened on my last install.

With the same installation image the directory is removed in VM.  But on real hardware the directory is not removed.

Base (multiple versions) Leaves my drivers behind at %systemdrive%\D

KTD is off, and they don't exist at the KTD location.
winnt.sif has DPsFnshr.exe listed and it does run.

DPsFnshr.ini wrote:

; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot    = "%SystemDrive%"
KTD = "false"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation    = "%SystemRoot%\DriverPacks"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%"
; enables/disables debug mode (enabled by default)
debug = "true"

DPsFnshr.log wrote:

2008-07-10 23:27:16 : <INIT> Detected a method 2 driver installation, the DevicePath value in the registry has been reset.
2008-07-10 23:27:16 : <FLTR> Collected the HWIDs for this system.
2008-07-10 23:27:16 : <FLTR> Verifying requirements for exception [NV3] (1 of 1 exceptions).
2008-07-10 23:27:16 : <FLTR>     2. +hwids (ANY +hwids must be matched)
2008-07-10 23:27:16 : <FLTR>         ! Could not match any of the +hwids.
2008-07-10 23:27:16 : <FLTR>     => This exception will not be applied.
2008-07-10 23:27:16 : <FLTR> Finished filtering exceptions.
2008-07-10 23:27:16 : <DBG>  0 exceptions have forfilled the requirements to be executed!
2008-07-10 23:27:16 : <KTD>  KTD will not be applied, the DriverPacks will be deleted.
2008-07-10 23:28:44 : <CLNP> Could not delete the DriverPacks, which are located in "C:\D".
2008-07-10 23:28:44 : <CLNP> Added new value to the RunOnce key in the registry: the cleanup of the "C:\D" directory will be retried (through CLI, not through the Finisher) after a reboot.
2008-07-10 23:28:44 : <CLNP> Deleted "C:\hwids.dat"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\DPsFnshr.ini"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\devcon.exe"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\makePNF.exe"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\pmtimer.exe"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\DSPdsblr.exe"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\DriverPack_*.ini"!
2008-07-10 23:28:44 : <CLNP> Deleted "C:\mute.exe"!
2008-07-10 23:28:44 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2008-07-10 23:28:44 : Program terminated.

forfilled lol

C:\D is read-only but rd /s /q takes care of it...

... Edit: title and first line by OverFlow ...

I meant to post here a while back but forgot.  806C is working great for me, thanks for implementing the fix.

SamLab:  Did you ever get VIA working on that other motherboard?

SamLab, if you want to test my VIA fix here's a modded 804h2.  Even though it's got an official sounding name it's unofficial.


Here's a page on PCI Class Codes:


I thought you had a good idea with 804h, but it didn't work for me sad

I'm having same problem with 8.04 and 8.04f test pack. I have

Moving V4 in front of V did not help, 3 cds down but I'm going to investigate this and report a fix.

Okay, here's my fix, tested and working:

edit .ini:

add PCI\VEN_1106&DEV_3149&CC_0101 to [V3], remove PCI\VEN_1106&DEV_3149&CC_0101 from [V4]


add %VT8237.SATA.DeviceDesc%  = vide_PATA_Inst_x32,PCI\VEN_1106&DEV_3149&CC_0101   ;VT8237 SATA Controller to [VIA_MiniIDE]

add VT8237.SATA.DeviceDesc           = "VIA Serial ATA Controller - 3149" to [Strings]

edit V4\VIPRT.INF:

remove PCI\VEN_1106&DEV_3149&CC_0101


(1 replies, posted in DriverPack WLAN)

Ralink RT2860

For support of Encore ENLWI-N, ENPWI-N, and other cards with this chipset.

Product page: http://www.encore-usa.com/product_item. … mp;pid=269
Direct link: http://www.encore-usa.com/download/driv … Driver.zip

Already extracted inf, sys, cat:

Pack is tested and working for ENLWI-N.

Wouldn't it make more sense to organize the LAN/WLAN packs according to chipset?