Topic: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

http://img95.imageshack.us/img95/1921/ktd9ee.th.jpg

It leaves some files behind on C:\ , is this normal?

Last edited by Bâshrat the Sneaky (2006-07-26 02:42:45)

http://www.l33tsig.net/sig/1/muiz.png

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

Hm, the log files are normal (obviously!), but the D folder shouldn't be there.
At least, it never was for me, but when I installed yesterday, with the settings I've been using five times before, it didn't get deleted, either.

About to reinstall anyway since there's new Sereby Packs out, but if you mind, check out those log files, maybe there was an error when it tried to delete the D folder...

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

The D folder is supposed to remain when KtD is enabled.  This is where the drivers are. wink

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

Yes, I know, but I never use KtD (always disabled), so this is a bit strange, huh?

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

i think these *.cmd and *.exe files on C:\ are not normal thing

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

Hi all, initially i thought i was the only person who suffered from this strange problem. Now i guess i have company. big_smile

Yep, even though i have disabled "KTD" feature in Driverpack BASE, all those extra files and folders shown in the upload pix exists in my BOOT drive too.

If Bâshrat needs any log files that may help him to diagnose or what, please feel free to ask.

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

Two issues I saw in Base 6.06 that are likely causes of this:

1. In cmdlines.txt, there is an extra double-quote after the "DPs_ROE.cmd" line. This means that the DP cleanup batch file doesn't get added to the RunOnceEx list.

2. In DPs_fnsh.cmd, there are two references to ELSEIF instead of ELSE IF (lines 378 and 384).

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

I noticed some issues in DPs_fnsh.cmd. in both :KTD_M2 :KTD_M1

%CDDRIVE%\OEM\bin\KTDpaths.cmd
%CDDRIVE%\OEM\bin\KTDpatterns.cmd
%SystemDrive%\KTDpaths.cmd
%SystemDrive%\KTDpatterns.cmd

Shouldn't they be?

START /WAIT %CDDRIVE%\OEM\bin\KTDpaths.cmd
START /WAIT %CDDRIVE%\OEM\bin\KTDpatterns.cmd
START /WAIT %SystemDrive%\KTDpaths.cmd
START /WAIT %SystemDrive%\KTDpatterns.cmd

The problem with this is the actions in those commands arn't logged in the DPs_fnsh.log.
Without "start /wait" they get logged but DPs_fnsh.cmd terminates & there's no cleanup.

Note: This only affects KTD Paths or KTD Patterns.

Last edited by Ron5000 (2006-06-20 15:01:38)

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

find some errors on DPs_fnsh.cmd (as always tongue )

on :EXCEPTIONS label

...REM |   Workaround for nVidia nForce 3 ethernet.
...
devcon update "%DriverPacks%\L\NV\123\nvnetbus.inf" "PCI\VEN_10DE&DEV_00DF&SUBSYS_E0001458&REV_A2" > NULL
devcon update "%DriverPacks%\L\NV\123\nvnetfd.inf" "{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV*" > NULL

NULL must be NUL

on :KTD_M1 label

... ) ELSEIF EXIST %SystemDrive%\KTDpatterns.cmd ( 
...
) ELSEIF EXIST %SystemDrive%\makePNF.exe (...

ELSEIF must be ELSE IF

on :CLEANUP label

IF ktd==no (...

ktd must be %ktd%

Last edited by laura (2006-06-20 04:49:42)

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

I noticed when I set only the 3rd party packs in KTD, *all* drivers were kept.

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

I noticed when i set it to disable KTD it also leaves all those things behind.
No matter what  my settings are , it doesnt cleanup.

http://www.l33tsig.net/sig/1/muiz.png

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

Can anybody solve this problem? I only use driverpacks base 6.06.1 and DP_MassStorage_wnt5_x86-32_6031.7z.This problem really exist. I'v tried many times.

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

muiz wrote:

http://img95.imageshack.us/img95/1921/ktd9ee.th.jpg

It leaves some files behind on C:\ , is this normal?

same problem
  thanks

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

I believe I agree with all the problems mentioned above plus.
There needs to be an ‘EXIT’ at the end of the batch files. So, when they are called from another program/script they leave a proper exit.

Example when using:

start /wait DPs_fnsh.cmd

Your left hanging.

I really wish these batch files would get fixed. This does not create great trust even with all the enthusiasm I have for this project.

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

In addition to the above errors, the "ktd" variable is never set to "NO" if you use method 1

I added "set ktd=no" under the editable variables section, and this deleted the drivers for me.

Last edited by Modulesix (2006-07-09 07:54:46)

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

I have the same problem (see picture below), but I've found a quick and simple solution.
At the end of Windows installation, I simply use this script :

:: ============================================================================
RD /S /Q %SystemDrive%\D
DEL /F /Q %SystemDrive%\CloseDSP.exe
DEL /F /Q %SystemDrive%\hideMakePNF.exe
DEL /F /Q %SystemDrive%\robocopy.exe
DEL /F /Q %SystemDrive%\WatchDSP.exe
IF EXIST %SystemDrive%\KTDpaths.cmd DEL /F /Q %SystemDrive%\KTDpaths.cmd
IF EXIST %SystemDrive%\KTDpatterns.cmd DEL /F /Q %SystemDrive%\KTDpatterns.cmd
DEL /F /Q %SystemDrive%\addUsepmtimer.exe
DEL /F /Q %SystemDrive%\agrep.exe
DEL /F /Q %SystemDrive%\devcon.exe
DEL /F /Q %SystemDrive%\fnsh_log.cmd
DEL /F /Q %SystemDrive%\DPs_fnsh.cmd
DEL /F /Q %SystemDrive%\DPS_fnsh.log
:: ============================================================================

http://img481.imageshack.us/img481/9850/driverpack9nt.gif

http://img136.imageshack.us/img136/9877/cocciwayoflifero0.jpg

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

cmdow @ /HID

RD /S /Q "%SystemDrive%\D"
DEL "%systemdrive%\agrep.exe"
DEL "%systemdrive%\devcon.exe"
DEL "%systemdrive%\DPs_fnsh.cmd"
DEL "%systemdrive%\fnsh_log.cmd"
DEL "%systemdrive%\addUsepmtimer.exe"
DEL "%systemdrive%\D\Addition 13-Apr-06.txt"
DEL "%systemdrive%\D\Addition 05-Jun-06.txt"
DEL "%systemdrive%\D\SupportList - DP Modem.txt"

EXIT

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

You may want to keep the log files, else they'd be completely useless if you have the script that creates them also delete them right away w/o giving you the chance to have a look at them.

Unless you really don't care...

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

i dont care wink

Last edited by muiz3 (2006-07-20 10:30:13)

Re: SOLVED BUG #87: when KTD is enabled, cleanup does not work as expected

Submitted to the bugtracker: bug #87, since no one had already done so.

Fixed in 6.07: no more batch file to finish the installation, but a worthy successor: DriverPacks Finisher, with better logging output etc.

Founder of DriverPacks.net — wimleers.com