1 Reply by Doodoo

(19 replies, posted in Feature Requests)

OverFlow wrote:

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.

Go to forum: Feature Requests

2 Reply by Doodoo

(19 replies, posted in Feature Requests)

Helmi wrote:

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

Go to forum: Feature Requests

3 Reply by Doodoo

(19 replies, posted in Feature Requests)

OverFlow wrote:

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.

OverFlow wrote:

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

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.

OverFlow wrote:

Interested in helping us test?

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"

Go to forum: Feature Requests

4 Reply by Doodoo

(19 replies, posted in Feature Requests)

cdob wrote:

Well, the refernce goes to msfn.org.

roll I guess I'm reading too many forums at once

cdob wrote:

A possible dumb user wink suggested a simple dir  && ( )

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 ?

cdob wrote:

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

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

Go to forum: Feature Requests

5 Reply by Doodoo

(19 replies, posted in Feature Requests)

BigBrit wrote:

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:

BigBrit wrote:

Don't know if this helps

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.

Go to forum: Feature Requests

6 Reply by Doodoo

(19 replies, posted in Feature Requests)

mr_smartepants wrote:

Well possibly.
The safest option is to disconnect any internal card readers during setup.  Once XP is loaded, you can reconnect them.

Unfortunately that's not really an option, e.g. for laptops with integrated card readers. Even for desktops, I don't want to spend my time opening the case, disconnecting the stuff, etc...

mr_smartepants wrote:

It has to do with how/when drive letters are handed out.  For some reason, XP likes to make card readers C, D, E, etc drives and the hard drives start somewhere around G, H, etc depending on how many devices are detected.

Yes and no. In fact if you read what they say in the link I have posted in my first message, the problem is that windows assigns drive letters to card readers even when no media is inserted.

In this case, presetup.cmd throws an error, when it tries to identify the location of the OEM folder. The reason is, it relies on the shell command "IF EXIST" which causes an error when used on a drive with no media inserted.

However there is a workaround, described in the link above once again.
I just thought it would be nice and easy to adopt their solution....

Go to forum: Feature Requests

7 Topic by Doodoo

(19 replies, posted in Feature Requests)

Hi everyone,

I keep having problems with computers having internal card readers, because when the GUI part of Windows Setup starts, it always throws an error "No Disk. exception processing message c0000013".

Actually if you clik "continue" setup will genuinely continue, and as fas as I can tell, it looks like everything is fine once setup is finished. The only problem is that unattended installs suddenly cannot be unattended anymore...

I just wondered if presetup.cmd could be fixed, with the following solution:

http://www.msfn.org/board/topic/137714- … _p__895361

or possibly a refined version:

http://www.msfn.org/board/topic/137714- … _p__895411

Hope that helps !

Go to forum: Feature Requests