Minor Bug Report for GM

[urgan]

XPCreate can stop waiting for a overwrite confirmation (even if not visible) if in two hotfixes in different subdirs happen to generate the same SHORTNAME.

For example, i had "WindowsMedia-KB832353-ENU.exe" on SVC-POS and "Windows-KB870669-x86-ENU.exe" on SVC-HF2, and since both got copied as WINDOW~1.EXE XPCreate was waiting for a Y/N/A answer to overwriting prompt when copying for some temp dir.

Since this is not probably simple to resolve now, i simply rename my hotfixes to short names before xppcreate processes them.

Hope you unterstood the explanation.

[GreenMachine]

Thanks, urgan, for pointing that out. Sounds logical, but strange that I've not run across it earlier. I must admit, I wish it wasn't true ... I guess my easiest option is to copy them all together with long file names first, and then with short file names after. What's a few more hundred Mbytes: XPCREATE already needs a couple Gbytes ...

Thanks again.

[urgan]

You're welcome

Probably I did some mistake, that's why this bug (not really) showed.

I was wondering, maybe it's possible (how to extract this in a batch?) to rename them related to the six digit id.

In case of collision (i'm thinking of the xml4 and xml3 hotfixes) add an extra letter or number.

Q832353A.EXE or 832353-1.EXE.

And if the name is already in 8.3 format use it when copying. This way it would generate a clean svcpack, without names like "foobar~1", better suited to tweak, comment or update manually. Just a thought, because i did rename the hotfixes and mend the svcpack manually once for clarity sake.

As a quick fix (and note this will only happenned when using non critical hotfixes), maybe it could have a counter and just rename them sequentially since the resulting names are somewhat irrelevant anyway for most users.

HOTFIX01.EXE, etc

I'm sure you too have plenty more ideas of how to improve it, (iso with build time in name ?) but you are probaby reaching the limits of what can be done in a batch file anyway.

cheers,

[GreenMachine]

Thanks again, urgan, for your ideas. We are far from the limits of a Command Script, it's just that they scare most people from going further.

The Type I hotfixes are renamed according to their hotfix number. The Type II presented a problem, so I dropped that. I'm not sure yet which route I'll take, but there are certainly many options.

If named with 8.3 conventions from the get go, the names will be kept. I think ... at least for Type I and Type II hotfixes. In any event I am certainly not too picky what the name is, as long as it doesn't create a conflict. I am not one that wants to remove directories or change names just because they are not pretty: I've learned long ago to simply direct my attention elsewhere.

So, thanks for the food for thought. I'm not sure this will make it into the next update, but even minor bugs do merit correction!