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

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

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

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

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

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.

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)

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

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.

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.

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
:: ============================================================================

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

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!