DriverPacks.net Forum - IMPLEMENTED: custom KTD location option

Re: IMPLEMENTED: custom KTD location option

null@example.com (Wim Leers) — Tue, 25 Jul 2006 15:43:19 +0000

Implemented now

Re: IMPLEMENTED: custom KTD location option

null@example.com (Denney) — Sat, 27 May 2006 12:50:42 +0000

Ah ok kool. I'll just edit the scripts for now.

You've edited the presetup.cmd file now and removed the variable to set where it's stored... Damn you...

Re: IMPLEMENTED: custom KTD location option

null@example.com (Wim Leers) — Sat, 27 May 2006 12:31:41 +0000

Hmm... You can interpret that line in two ways:

1. The thing you mean: where KTD drivers are stored.

2. The way I implemented it: you can specify paths on which KTD will be applied.

I'll see if it's much work to add it... It will be added, but perhaps only after my exams.

IMPLEMENTED: custom KTD location option

null@example.com (Denney) — Sat, 27 May 2006 12:15:55 +0000

According to the MSFN post (http://www.msfn.org/board/index.php?showtopic=66854) there is support for a custom path for the KtD option. I can't seem to find that option though.

I like to keep the drivers in the "%SystemRoot%\D" directory (not "%SystemDrive%\D") and I've always changed it via manually editing the .cmd files. I hoped not to have to do this with the new version.

Was this option scraped at the last minute or is it hidden somewhere?