8 replies to this topic

[pscEx]

When testing the new BootSDI sript, I recognized missing harddrives under W2003.
That is not an issue of BootSDI, the 'normal' ISO shows the same behaviour.

I'm rather sure that this is again an hivesFactory issue and will check that.

Some help?
(You can preserve the hives etc. scripts by setting Debug to 1 in !WBManager, Fundamentals).

Peter

[Oleg_II]

You mean: when you load with build you can't see your hard disk? Or you can't see it when you reboot in normal system after testing a build?

[pscEx]

You mean: when you load with build you can't see your hard disk? Or you can't see it when you reboot in normal system after testing a build?

If you look to the screenshot pinned in nativeEx:
You see the (VMWare own) harddrive C:
If the ISO is build from W2003, this drive C: is not present.

I did not test booting my system from a real CD, but I'm sure the behaviour is identical.

Peter

[Oleg_II]

If I can get my testing computer working tomorrow I'll test it with Win2003 source on a real computer

PS Just remembered: I don't use VMWare but I heard it can emulate SCSI drives and if I'm not mistaken there are even drivers for it. Could it be that WinPe without these drivers can't see your SCSI disk?

[pscEx]

If I can get my testing computer working tomorrow I'll test it with Win2003 source on a real computer

PS Just remembered: I don't use VMWare but I heard it can emulate SCSI drives and if I'm not mistaken there are even drivers for it. Could it be that WinPe without these drivers can't see your SCSI disk?

Thanks that you want to test.
But you can save the time.

I just made a test with 052 standard project (predefined hives and txtsetup.sif).
Here the C: drive is visible in both sources, XP SP2 and W2003.

So the issue is really introduced by the new created hives and/or txtsetup.sif (my work )

BTW: You can easily test by using qEmu: You (don't) see the swiss knife C:

Peter

[pscEx]

I brought the issue down to lowest level of reproduction:

In nativeEX_barebone (download latest updates!) try this:

It gives you a qEmu ISO boot into cmd, no apps, no drivers etc.

dir C:
Built from XP it shows the 'swiss knife' qEmu HDD.
Built from W2003 thre is no drive C:

Peter

[pscEx]

I got it!

The reason was very simple (but hard work to find):
In W2003 txtsetup.sif there is a line

STORAGE\Volume="volsnap",{71A27CDD-812A-11D0-BEC7-08002BE2092F}

under

[HardwareIdsDatabase]

Which propably causes some (unfinished) investigations of W2003.
I removed the line and everything is ok.
Upload of new hiveFactory script to nativeEx_barebone server is done.

But the BIG COMPETITION for all experts: What happens during setup when executing this line????


Peter

[was_jaclaz]

volsnap.sys:

http://support.micro...kb/924058/en-us


appears to be a driver for "shadow-volumes":
http://msdn.microsof...r_providers.asp

You can also try with the updated ones:
http://support.micro...kb/887827/en-us
(or at least from there you should get the list of all "involved" files, maybe another one is missing/mis-configured)

jaclaz

[pscEx]

volsnap.sys:

http://support.micro...kb/924058/en-us


appears to be a driver for "shadow-volumes":
http://msdn.microsof...r_providers.asp

You can also try with the updated ones:
http://support.micro...kb/887827/en-us
(or at least from there you should get the list of all "involved" files, maybe another one is missing/mis-configured)

jaclaz

Thanks, Jaclaz
I'll see whether me (and the solution) is satisfied with the version w/o volsnap.
Maybe I use your info to build the volsnap stuff for W2003 sources (???)

Peter