It is in the head version that did not get released.   Haven't worked on it in a long time.
Guess i have a reason now

PS you can edit the presetup.cmd file yourself for the time being. (as you know)

Implemented with latest test ver

Hmmm as far as I can tell, it's still not part of the current DriverPacks BASE 10.06
This bug is minor but is really (I mean really) annoying....
Is that something can be fixed once and for all please ? I think the fix in post #17 probably is the best option.

DIR %%i: && IF EXIST "%%i:%TAGFILE%"

I'll get that out to the testing team in my next nightly

Moved to Feature Requests forum

Maybe it depends on the make or model of the reader or it's down to the BIOS.

Yes very possibly, could be a very peculiar issue.
Anyway, replacing

IF EXIST "%%i:%TAGFILE%"

with

DIR %%i: && IF EXIST "%%i:%TAGFILE%"

entirely solves the problem

With the rising number of integrated card readers, I'm surprised there aren't more people who have problems though. Maybe I am the only one having this problem because I'm installing from USB, not from CD.

Well, what can I say, I also use card readers in all of my systems, none of them gives me any problems when installing.
Maybe it depends on the make or model of the reader or it's down to the BIOS.
I'm not entriely sure as most installs have been from DVD, but at least on notebooks, installing from USB wasn't affecting this.

A similar solution was posted here several years ago...
it was the first suggestion offered, reverse the drive search order...

Yep, that's another solution, also discussed in the same thread on MSFN:
http://www.msfn.org/board/topic/137714- … _p__895119

However, it's not garanteed to work all the time... It just happens to work if the OEM folder is found before the (empty) card reader slots are scanned. I think any of the other workarounds above are much cleaner and safer.

With the rising number of integrated card readers, I'm surprised there aren't more people who have problems though. Maybe I am the only one having this problem because I'm installing from USB, not from CD.

I wish I could but with a 3-month old baby to look after I'm quite busy these days... also at night ;-)
I can report that this solution:
http://www.msfn.org/board/topic/137714- … _p__895411
works like a charm, though, whereas the current implementation causes the "c0000013 error"

It's not that common of a problem, and the various workarounds are easy enough...
It never really became a priority

this probably should have been posted in feature requests, not in feedback and support.

I'll take a look at the options presented and see what think is the best option and we will do some testing... Interested in helping us test?

jeff

Well, the refernce goes to msfn.org.

I guess I'm reading too many forums at once

Sorry I didn't mention your solution, cdob.... In fact it's indeed very simple and very elegant. At first sight I thought it was not entirely working, for both 32- and 64-bit ? But in fact it is working for both, right ?

Well yes... It is quite safer to assume that COMMAND.COM is present rather than MOUNTVOL.EXE

that these clever guys at boot-land.net

Well, the refernce goes to msfn.org.
A possible dumb user suggested a simple dir  && ( )
http://www.msfn.org/board/topic/137714- … _p__895386

A most clever end user may have remove mountvol.exe.
It's recommended to rely at a possible missing file?

Stu

Sorry the idea did not work for you and yes we do appreciate challenges and people who find a fix and share it.

Good luck to you.

Stu

If it shows up as H: whatever during the install, let the format start and then reboot. You should find the HD will show up as C: on the next format.
Stu

Thanks for the tip, it's true that the partition you where want to install XP doesn't always show up as C:

Well no I'm afraid. The problem appears when the GUI part of setup starts (after the TXT part of setup has finished, and the PC reboots).
This is exactly when the DriverPacks are decompressed and presetp.cmd is launched.

Maybe it wasn't clear in my message: I am not looking for any help or any solutions.
I just wanted to let you know that these clever guys at boot-land.net have already found a solution and it would be nice to make it part of the next DriverPack BASE release.