Thus, use this link which will open the page of Archive. Just on the same page, the free but official professional key for the same will have been given. Copy that and jot down somewhere like NotePad. Here is the link to Download VBox. In case you already have the Vbox on your system then simply move to next. The installation of the VBox is like any other executable software meant for Windows nothing will be complicated at all.
Run VirtualBox and click on the New button given on the Menu of it. Now in the Name box, type- Windows XP and its corresponding options will automatically get setup. Then click on the Next button. To store the installation file we need to attach a Virtual Hard drive to our Virtual Machine. The VirtualBox will automatically set it to 10GB which is enough.
Why is it, with a clean and good install of XP Pro 32bit , all working fine including IE, it stops working once XP is installed on a separate partition? Frolin ,. You're not installing the NIC drivers on the data partition, are you? Log in or Sign up to hide this advert. Yes, am loading the drivers for the Marvel NIC card in both sides.
Then go to load XP and do the same steps, drivers then programs. Thought maybe reload, could not. So tried to uninstall, could not, tried to disable, could not. When try to disable or uninstall, routine hangs every time. Lost you there! My point is that the drivers must be installed on each OS partition. If installed on the data drive the first install gets overwriten by the second, which could explain what's happening. Ah, good point! What I did, was create one huge task sequence that creates 2 partitions, installs windows xp first on the first partition, and then install windows 7 on the second partition.
So far this logic makes sense Since the installations pull their unattended settings from unattend. And that's where this little adventure ended for me. Since my workday is done now, and I really dont wanna spend time on this at home other then sending this reply, I only have one more suggestion that should work though. It's not really a best practice solution, but it should do the trick for you.
First off, you'll need a deployment share, containing the W7 image you want to deploy, and create a fully automated LTI Lite Touch Installation by providing all necessary answers for settings in the customsettings. Create one task sequence for a standard client OS install, within this TS, disable the partition and format disk step and change the partition id to "2" you'd want windows 7 to install on your 2nd partition.
Now back to the Windows XP TS, at the end, you'll want to add another run command line step, and with this step you'll call the litetouch script from the second deploymentshare, since you made it fully automated, it will not ask for anything and launch the W7 install right off. Like I said, this is not really a best practice solution, but unless anyone else here has a better solution I'm eager to hear it not that I need it, but I always like to lean more!
This should work though, maybe if I have some spare time again tomorrow at work I'll give it a try since it's rather quick to setup anyway. I suppose you could also just expand the winxp TS, with a reboot to winpe, and from there on just call the setup manually and provide an unattend.
But if you'd have a fully customized image that needs nothing done to it anymore once it starts up, that'd be another way to do it, without needing a second deploymentshare. Are you trying to do this without losing the currently installed Windows XP, or do you plan on reinstalling both XP and W7-x64?
0コメント