jpw
March 24th, 2006, 04:09 AM
Hi, we have several sales people in the field and are looking for a reasonably user-friendly way for them to choose one of two XP partitions to boot each time they boot.
What we'd like to do is this:
1) COPY their existing partition (already running WinXP) to a second partition (also a primary)
2) have OS Selector give a menu of which partition to boot from
(In our case, we'll then install some special apps and data on the second partition, and we do not want apps or malware on the first partition to have access to the data on the second partition. The second partition won't even have internet access enabled, for example. So we'll have our sales people boot into ne or the other partition depending on what they are doing.)
And what we'd like is when they boot from partition A then partition B is not accessible (until the next time they chosoe which to boot from).
I saw on some support replies a generic reference to a Microsoft article about having to modifying the boot.ini file to recognize the second partition's OS? If so, could you supply the EXACT steps needed to make your software "see" the second copy of the XP (on the copied partition)?
For example, the Microsoft article says generically:
At the command prompt, type:
bootcfg /copy /d Operating System Description /ID#
But what goes in the ID# field? After we copy the partition, how do we correlate what Disk Director has done with what the boot.ini file is expecting?
Thanks!
P.S. This seems to be a common enough question that you might want to have a nice detailed FAQ -- or even better, modify the software so it just does it automatically -- if you copy a partition with XP on it, it's a reasonable expectation that your OS Selector would give you a choice of which one you want to boot from.
What we'd like to do is this:
1) COPY their existing partition (already running WinXP) to a second partition (also a primary)
2) have OS Selector give a menu of which partition to boot from
(In our case, we'll then install some special apps and data on the second partition, and we do not want apps or malware on the first partition to have access to the data on the second partition. The second partition won't even have internet access enabled, for example. So we'll have our sales people boot into ne or the other partition depending on what they are doing.)
And what we'd like is when they boot from partition A then partition B is not accessible (until the next time they chosoe which to boot from).
I saw on some support replies a generic reference to a Microsoft article about having to modifying the boot.ini file to recognize the second partition's OS? If so, could you supply the EXACT steps needed to make your software "see" the second copy of the XP (on the copied partition)?
For example, the Microsoft article says generically:
At the command prompt, type:
bootcfg /copy /d Operating System Description /ID#
But what goes in the ID# field? After we copy the partition, how do we correlate what Disk Director has done with what the boot.ini file is expecting?
Thanks!
P.S. This seems to be a common enough question that you might want to have a nice detailed FAQ -- or even better, modify the software so it just does it automatically -- if you copy a partition with XP on it, it's a reasonable expectation that your OS Selector would give you a choice of which one you want to boot from.