Hello,
Is it possible to use a single PC w/ Multiple Partitions for different OSs i,e, XP-32, XP-64, Vista-32, Vista-64 etc as a DTM client ? We are trying to install the DTM client under each partition and have noticed that the Client installer does overwrite an existing \WTT dir on another partition other the the Current’s OS partition if one exists elsewhere.
We installed
XP 32 bit on Partition 1
XP 64 bit on Partition 2
Vista 32 bit on Partition 3
Vista 64 bit on Partition 4
XP 32 installed and registered in DTM Studio. Then we installed the client on the XP 64 install and notice that the WTT folder did not install on the System partition. It installed on the same partition as XP 32. Now when ever we boot XP 32 or 64, that will be the only one showing in DTM Studio.
We also tried to install on Vista 32 and 64 and again, the same problem where only one of the 4 OSes will show in DTM studio.
We tried to see if we could trick the client installer by installing on XP 32 and making sure it worked. Then we stopped the service and zipped up and hid the \WTT folder and proceeded with an install on XP 64 partition doing the same. The same for Vista 32 and Vista 64. So no install saw a \WTT folder on any other drive during install. Still after the installs of the clients. all with what appears to be their own \WTT folder on their system partition, the DTM server would only show the one OS at a time knowing it was the same computer.
We even went a step further by putting a small hack in place by overriding the MAC address for the network card. This should produce a slightly different computer configuration and also forces each partition to have its own IP address, but that did not help either.
This machine can have a “system GUID” hardcoded in the BIOS.
Then it identifies the machine, rather than the MAC address.
–pa
wrote in message news:xxxxx@ntdev…
> Hello,
>
> Is it possible to use a single PC w/ Multiple Partitions for different OSs
> i,e, XP-32, XP-64, Vista-32, Vista-64 etc as a DTM client ? We are trying
> to install the DTM client under each partition and have noticed that the
> Client installer does overwrite an existing \WTT dir on another partition
> other the the Current’s OS partition if one exists elsewhere.
>
> We installed
>
> XP 32 bit on Partition 1
> XP 64 bit on Partition 2
> Vista 32 bit on Partition 3
> Vista 64 bit on Partition 4
>
> XP 32 installed and registered in DTM Studio. Then we installed the
> client on the XP 64 install and notice that the WTT folder did not install
> on the System partition. It installed on the same partition as XP 32.
> Now when ever we boot XP 32 or 64, that will be the only one showing in
> DTM Studio.
>
> We also tried to install on Vista 32 and 64 and again, the same problem
> where only one of the 4 OSes will show in DTM studio.
>
> We tried to see if we could trick the client installer by installing on XP
> 32 and making sure it worked. Then we stopped the service and zipped up
> and hid the \WTT folder and proceeded with an install on XP 64 partition
> doing the same. The same for Vista 32 and Vista 64. So no install saw a
> \WTT folder on any other drive during install. Still after the installs
> of the clients. all with what appears to be their own \WTT folder on their
> system partition, the DTM server would only show the one OS at a time
> knowing it was the same computer.
>
> We even went a step further by putting a small hack in place by overriding
> the MAC address for the network card. This should produce a slightly
> different computer configuration and also forces each partition to have
> its own IP address, but that did not help either.
>
>
>
> Is it possible to use a single PC w/ Multiple Partitions for different OSs i,e, XP-32, XP-64, Vista-32, Vista-64 etc as a DTM client ?
Like trying to kernel debug with only one PC, DTM is much easier if you have more than one. And quicker! Unclassified USB on Windows 7 takes a good 6 hours. I don’t want to wait 12 hours for 32bit and 64bit to finish.
Regards,
Tim.
Thank you both for your replies
We will have to look if there any way around this “system GUID” hardcoded in the BIOS.
unless you know of any
> This machine can have a “system GUID” hardcoded in the BIOS. Then it identifies the machine,
rather than the MAC address.
WEll, although SMBIOS allows an ID, it does not require MB vendor to provide it. Therefore, in quite a few cases the whole thing will be something meaningless like MB123456789. This is why relying upon BIOS ID is no-so-wise approach for a product that is meant to run on any machine. Therefore, I don’t think Windows actually makes any use of it …
Concerning the OP’s problem, there is no guarantee that he will be able to override MAC address successfully - although he can change the registry settings for MAC address that the machine uses, he cannot do anything about the one physically burnt into the chip…
Anton Bassov