Installing Vista on your Toshiba M200
I wanted to install Windows Vista on my Toshiba M200 TabletPC. However, I have no optical or floppy drive, making it difficult to install a new OS the usual way (boot from CD or install boot disk). These instructions should apply to anyone that has a computer without an optical drive. You will need a second computer running Windows to act as your "technician computer". This is the machine where you will do most of the work. Throughout this guide I will refer to the two computers you are working with as the "technician computer" and the "target computer". The two computers must be on the same network.
The Easy Way
If you meet all of the following requirements, the process is much simpler:
- Your target computer (in my case, the M200) is already running an older version of Windows
- You do not need to re-partition or re-format your hard drive. You are okay with letting Vista just create a new Windows folder (renaming your current Windows folder to Windows.old), and keeping the rest of your hard drive in tact.
If that fits your situation, follow these instructions:
- If you have a Vista DVD, and a DVD drive on your technician computer, put the DVD in the drive. If you have an .ISO image of the Vista DVD, mount the .ISO using a program like VirtualCD or Nero ImageDrive.
- Use Windows Explorer to share the drive with your network (right-click, Sharing and Security, Share this drive).
- Boot into the existing Windows on the target computer. Map a drive to the share on the technician computer (Windows Explorer, Tools menu, Map Network Drive). Map drive Y: to \\othercomputer\sharename
- On the target computer, run setup.exe from the network drive (Y:\setup.exe).
The Vista installation will begin. The only limitation is that you cannot re-format the hard drive on the target computer. It says you need to boot from the installation media if you want to change the target hard drive. Since we don't have a CD\DVD drive, things get more complicated. If you are like me and wanted to start from a clean slate - and have a lot more time to spare ;) - read on. Otherwise, enjoy your new Vista computer.
The Hard Way
If you insist on reformatting your hard drive, you will need to boot the target computer using network PXE.
What you will need
- A computer that supports PXE booting from the network (the Toshiba M200 does). Check your BIOS boot precedence options.
- Everything in the "what you will need section" of PXE Booting your M200 to DOS using a Windows Server
- The Windows Automated Installation Kit (WAIK) UPDATE: The WAIK download link is back - thanks for the note Miguel.
- Microsoft Virtual PC 2004 (or access to a computer already running Windows Vista)
Setup your PXE server
Setting up a PXE server using Windows XP (and probably other flavors of Windows - I only tried XP) is surprisingly simple. Just follow the instructions (up through step 13) from PXE Booting your M200 to DOS using a Windows Server. Before proceeding with the Vista install, I highly recommend following all of the steps on that page to boot your computer to DOS. This will verify that you can successfully deliver a PXE boot image to your target computer. Also, I advise you to use the msnet bootdisk image as mentioned in the article so that you can verify connectivity to the rest of your network. You will want to make sure that you can connect to a share on your technician computer from your target computer (currently running DOS). One part I stumbled on is that DOS does not let you provide a username\password when connecting to a share with "NET USE". You need to use the "Logon" feature when the network is first configured at boot. Use a valid username\password that exists on the technician computer. Now when you map a share with NET USE, it will pass those credentials and grant you access.
UPDATE: Some TFTPD32 users are reporting that they need to make sure the "PXE compatibility" option is selected to get the process to work. Thanks to Jonathan Payan for the suggestion. It worked successfully for me without enabling that option, but if you are having trouble, it is worth trying.
Unfortunately, you cannot run the Vista install from DOS. If that were the case, you would simply have to share a folder (or drive) on your technician computer containing the Vista install, map a drive to it from the target computer, and run setup.exe. Instead, invoking Vista's setup.exe will give you an error message that it cannot run from DOS.
Running Windows PE 2.0
The solution is to boot your target computer into Windows PE 2.0, which is the Vista equivalent of a DOS boot disk (with MUCH more capabilities). You cannot download Windows PE 2.0 (that I know of), so you need to create your own PE image using the Windows Automated Installation Kit (WAIK). Download the image at that link, rename the .img file to .iso, and either mount it using VirtualCD, some other ISO disk mounter, or burn it to a CD. Once you can read the disk image, run the setup to install WAIK on your technician computer.
Unfortunately, one of the steps to create a version of Windows PE 2.0 that can be booted from the network must be performed on a computer already running Windows Vista (or PE 2.0). If you have access to such a machine, you can skip ahead to "Creating a Windows PE 2.0 PXE Installation". Otherwise, use the following steps to get a minimalist Windows PE 2.0 up and running:
- Download and install Microsoft Virtual PC 2004. Create a new virtual machine with 512MB RAM. The hard drive size does not matter, as it will not be used.
- On your technician computer (with WAIK installed), run the "Windows PE Tools Command Prompt" from your start menu.
- Enter the following commands:
copype x86 c:\winpe
oscdimg -n -bc:\winpe\etfsboot.com c:\winpe\ISO c:\winpe\winpe.iso
You now have a bootable Windows PE 2.0 CD ISO image. Start your new virtual machine, choose "Capture ISO image" from the CD menu, and select the c:\winpe\winpe.iso that you just created. It will boot into Windows PE 2.0, which you can use to run BCEDIT in Step 2 of the next section.
Creating a Windows PE 2.0 PXE Installation
UPDATE: Apparently this mix between the Microsoft documentation and my documentation has confused a number of people, and they are ending up with invalid BCD files. I have written a new post that explicitly shows the commands I entered. Hopefully this will help clarify which steps people are doing incorrectly. After following the steps in Deploy a WinPE 2.0 image using PXE and the WAIK, you can jump back here and continue with the steps in "Running the Install".
Open the "Windows Automated Installation Kit User's Guide" help file that has been added to your start menu. Find the article "Walkthrough: Deploy an Image by using PXE" (switch to the Index tab, type PXE, and select the first article). Follow each of the steps in that article, with the following modifications/clarifications:
Step 1 - 4: You do not need to map a drive to your TFPT directory, since it is on your local system (it is the tftpboot folder created in step 2 of the M200 article mentioned above). Any time the WAIK article refers to Y:\, just substitute your tftpboot folder.
Step 1 - 5: The first command (cd \temp\Windows\Boot\PXE) seems to be an extraneous typo. Ignore it. Just proceed with the command to copy the files from the boot\pxe folder.
Step 2 - *: These are the steps that you need to run from your other Vista computer, or the Windows PE Virtual Machine. Not being familiar with the BCDEDIT syntax, these instructions confused me a bit. When I read the commands with braces in them (ex: {ramdiskoptions}), I thought I needed to substitute my appropriate values. Of course, not knowing what I was doing, I had no idea what values to substitute, so was a little stumped. It finally dawned on me that they weren't telling me to substitute my own values - they wanted me to literally type those characters: {ramdiskoptions}. Apparently, in BCDedit, you create nodes with names specified with braces.
Step 2 - 3: I skipped this step, as it is optional, and I wont be attaching a debugger during boot.
Step 2 - 4: Now, I just told you that when you see braces, you should enter it literally and not substitute a different value. Except for this step ;). For these commands, wherever you see {guid1}, you should substitute the guid (with surrounding braces) that was returned from the first command in 2-4. The command prompt copy/paste feature comes in really handy here (I wouldn't recommend hand typing the guid repeatedly - if you get it wrong, who knows what will happen).
Step 2 - 5: If you skipped the optional step 2-3 (as I did), you can ignore the "/inherit {dbgsettings}" at the end of the first line. Also, the last line has a typo - they forgot to include the name of the node you are editing. It should look like this:
Bcdedit -store c:\BCD -set {bootmgr} displayorder {guid1} (where {guid1} should be replaced with your own guid, as previously mentioned)
Step 2 - 6: You need to copy the BCD file you just created to the tftpboot\boot folder on your technician computer. One way is to share the tftpboot\boot folder, give write permissions to a user, map a drive to that share from your Vista/PE virtual machine, and copy the BCD file to the mapped drive.
Step 2 - 7: You do not need WDSNBP.COM. Instead, you can have your PXE server provide PXEBOOT.COM. Start tftpd32.exe and click on the DHCP tab. Change the "Boot file" from "pxelinux.0" (assuming you followed the instructions to boot to DOS) to "boot\pxeboot.com" (assuming you followed the instructions to copy the Vista PXE files to a boot subfolder).
Running the Install
Finally, boot your target computer using PXE. Now, instead of downloading and running the DOS boot disk, it should download and run pxeboot.com. Press F12 when prompted to boot from the network. Your target computer should now boot into Windows PE.
1) If you haven't yet, you need to create a share on your technician computer that contains the Vista installation media. You can copy the files from a DVD to local folder and share the folder, or just share your DVD drive like I did.
2) From the target computer (running Windows PE), map a drive to your new share:
NET USE y: \\servername\sharename
When prompted, provide a username\password that is valid on the technician computer.
3) Run Y:\setup.exe to begin the Vista installation. You can safely turn off your PXE server (tftpd32.exe).
Improving the M200 Vista Experience
When my Vista installation completed on my M200, it only had a standard VGA driver. I downloaded and installed the NVIDIA Windows XP driver for the M200 from the Toshiba support site to get back to the tablet's native resolution.
UPDATE: Thanks to a comment from DrTigerlilly, I now have working screen rotation on my M200. The trick is to install some packages intended for the M400. Go to the Toshiba Vista support page, click on Portege M400, then download and install the following 2 packages:
- Utility: driver_toshiba_value_added_package_v1.0.3.zip
- Buttons: driver_tabletpc_extension_v1.0.0.1.zip
Comments
The only option I had for reinstalling Windows on an R100 this past weekend was a network boot -- I would have been sunk without your instructions. Thank you very much.
--Drew
http://www.csdsupport.toshiba.com/tais/csd/support/windows_vista/vista_beta.cgi?lsAction=list_files&model_id=10
--Drew
I see flashing cursor in the top right corner for 30 seconds
and then the error shows up
File: \boot\BCD
Status: 0xc0000022
Info: An error occured while attempting to read the boot configuration data
I created BCD file following your instructions and copied it, what could be the problem ?
(x:\WindowsPE>) available so I used X:\BCD instead of C:\BCD
and therefore copied BCD file from virtual X: drive
is it OK ?
as far as I understand BCD will be the same for everybody.
Can you email me your BCD file?
Status: 0xc0000022
Info: An error occured while attempting to read the boot configuration data
why?
I did as you say (3 times), but always this error...
sorry for my english... :-)
http://flimflan.com/blog/DeployAWinPE20ImageUsingPXEAndTheWAIK.aspx
Hopefully that will help clarify which steps people are doing wrong. If you do realize what you did wrong and get it working, please post a comment on one of these articles so that others can learn from it.
http://flimflan.com/blog/DeployAWinPE20ImageUsingPXEAndTheWAIK.aspx
Hopefully that will help clarify which steps people are doing wrong. If you do realize what you did wrong and get it working, please post a comment on one of these articles so that others can learn from it.
DOES ANYONE HAVE A SOLUTION IN EITHER: just rebooting and installing Windows Vista without a password or some way of getting round this password. Anyone?????
PS: i have a pc that i can use and any solution please email me it to [email protected]
isn't the vista DVD bootable it self?
cant we just boot the vista DVD??
Moreover,
do you think the above step will work and help me boot my Norton Ghost over the network?
I'm pretty sure Norton Ghost has its own PXE server and client built in, so you really don't have to mess with anything mentioned in this article. If it doesn't, I'm sure you could use the TFTPD32 software as your server. The relevant information is in the article I linked to: http://home.allegiance.tv/~joem298/
When you install this program open up bdd 2007\deployment workbench in the star menu. Once open, expand the information center branch, click on components, and choose to download windows automated installation kit. This kit is large and took about 30 minutes on 8mbits cable.
Mine hung on me just after 100% at "copying". A restart of the program brough up an option to install. After installing, there will be a link in your start menu to the windows pe command prompt!
The only thing that threw me off with this entire article is on the second page, there's no spage between the drive and the shared computer.
Eg: net use y:\\computer vs. net use y: \\computer.
Also make sure when you enter your username and password, you enter it in the format
computer\user
password
good luck!
Download windows pe 2.0 form here
http://technet.microsoft.com/en-us/windowsvista/aa905120.aspx
or here
http://www.microsoft.com/technet/desktopdeployment/bdd/2007/default.mspx
or here
http://www.microsoft.com/downloads/details.aspx?familyid=13F05BE2-FD0E-4620-8CA6-1AAD6FC54741&displaylang=en&Hash=XDC3RyruFGjOGvzEzFHsn8QzzeNOCdzwu7360cPF%2bBJNIcxc%2fFA1fuaFg9Su9CMQmEM95shU5H8FxtDWS9RfBg%3d%3d
(version difference?)
<boot\pxeboot.com>: sent 49 blks, 25068 bytes in 1 s. 0 blk resent [11/02 14:54:28.171]
Connection received from 192.168.2.3 on port 2071 [11/02 14:54:28.659]
Read request for file <boot\bootmgr.exe>. Mode octet [11/02 14:54:28.661]
Using local port 49379 [11/02 14:54:28.663]
<boot\bootmgr.exe>: sent 817 blks, 417896 bytes in 1 s. 0 blk resent [11/02 14:54:29.840]
Connection received from 192.168.2.3 on port 10069 [11/02 14:54:30.143]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [11/02 14:54:30.145]
OACK: <tsize=47452,> [11/02 14:54:30.164]
Using local port 49380 [11/02 14:54:30.166]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [11/02 14:54:30.198]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [11/02 14:54:31.202]
OACK: <tsize=47452,> [11/02 14:54:31.287]
Using local port 49381 [11/02 14:54:31.294]
<Boot\Fonts\wgl4_boot.ttf>: sent 93 blks, 47452 bytes in 1 s. 0 blk resent [11/02 14:54:32.459]
Read request for file <\boot\boot.ini>. Mode octet [11/02 14:54:32.468]
File <boot\boot.ini> : error 2 in system call CreateFile The system cannot find the file specified. [11/02 14:54:32.482]
Connection received from 192.168.2.3 on port 10072 [11/02 14:54:48.390]
Read request for file <\Boot\BCD>. Mode octet [11/02 14:54:48.393]
OACK: <tsize=12288,> [11/02 14:54:48.417]
Using local port 49383 [11/02 14:54:48.420]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [11/02 14:54:48.440]
Read request for file <\Boot\BCD>. Mode octet [11/02 14:54:49.458]
OACK: <tsize=12288,> [11/02 14:54:49.507]
Using local port 49384 [11/02 14:54:49.512]
<Boot\BCD>: sent 25 blks, 12288 bytes in 1 s. 0 blk resent [11/02 14:54:50.606]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [11/02 14:54:50.642]
OACK: <tsize=47452,> [11/02 14:54:50.671]
Using local port 49385 [11/02 14:54:50.677]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [11/02 14:54:50.704]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [11/02 14:54:51.712]
OACK: <tsize=47452,> [11/02 14:54:51.744]
Using local port 49386 [11/02 14:54:51.751]
<Boot\Fonts\wgl4_boot.ttf>: sent 93 blks, 47452 bytes in 1 s. 0 blk resent [11/02 14:54:51.918]
Connection received from 192.168.2.3 on port 10076 [11/02 14:54:51.927]
Read request for file <\hiberfil.sys>. Mode octet [11/02 14:54:51.936]
File <hiberfil.sys> : error 2 in system call CreateFile The system cannot find the file specified. [11/02 14:54:51.943]
(I cut the top part off to make the post shorter)
For some reason, it is trying to look for boot.ini, which I dont think Windows Vista uses anymore) and it also wants hiberfil.sys. Is there something I may have missed out?
Any help will be greatly appreciated, thanks :)
Inter(r) 82801DB/DBM AC '97 Audio Controller.
Thanks for all your help guys, Ive finally got Vista up and running on my ASUS R2H!
Not sure it would really help. I have a USB audio interface device, so is not critical, but is a pain.
http://www.networkblog.net/tag/toshiba
Then, I got brave and got this from Toshiba:
http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=1671893&moid=893054&BV_SessionID=@@@@0770296019.1171570754@@@@&BV_EngineID=cccgaddkefiljhdcgfkceghdgngdgnj.0&ct=DL
Which will give you an executable: util_mute_off_25847B.exe
I ran it and it worked! The M200 was not listed as supported for this utility. But, I got brave.
Doing this throws an error code 0xc000000f. Reason for this is -
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=772243&SiteID=17
"This issue is caused by the fact that you are doing a PXE referral (that is what occurs when using DHCP Options 66 & 67) but are using the incorrect boot program. You should instead be pointing clients to download wdsnbp.com, a boot program specifically designed to fix-up the DHCP info in the BIOS as if the client directly contacted the PXE Server (as should be the case, per the PXE spec). "
Having seen that, I changed my boot program to wdsnbp. But again, I faced the "TFTP failed" issue mentioned in the above link. This looks like the original link that explains this tftp failed problem -
http://support.microsoft.com/kb/926172
I still don't know how to fix this. Let me know if someone has an idea.
Google for 'aik site:microsoft.com'
Miguel
I tried installing the util_mute_off_25847B.exe patch but still no luck.
Any help is highly appreciated!
Found an executable to turn mute off on an internal site.
Configuretion:
DHCP (linux) set to instruct the client to download pxelinux.0
pexelinux.cfg/default:
# Boot PE to install Vista etc...
label pe
kernel Boot\wdsnbp.com
any thoughts? It almost works...
I have filename remapping working too...
rg \\ / # Convert backslashes to slashes
HELP!!!
Please Help
I wanted to add my two cents in regards to Stephan's questions about chain-loading from pxelinux (two posts up).
I also had a perfectly working pxelinux setup before attempting this, so I too wanted to integrate it.
The first thing I did was to simply rename 'pxeboot.n12' to 'pxeboot.n12.0'. The 0 extention tells pxelinux to execute the file as "pxe" format. (In your 'pxelinux.cfg/default' file, you can also use "pxe Boot/pxeboot.n12" instead of "kernel Boot/pxeboot.n12" to do the same thing without renaming the file).
Finally, the 'bootmgr.exe' file has to be put in the root directory (the tftpboot directory on most setups) since this is the working directory on bootup.
That was all I had to do. As soon as pxelinux was executing the 'pxeboot.n12' file properly and 'bootmgr.exe' was in place, it loaded perfectly. Just as in the guide, I never used 'wdsnbp.com'.
If someone have them, is it possible to upload an image to a server (ftp or rapidshare for example) and give me the links?
I guess it is ok,since I already have the original windows sticker on the M200 and the recovery discks work only on the specific machine
Many thanks,
Stavros
The "Install Windows XP" button is grayed out when I run setup.exe. Does anyone know a way around this?
I've seen references saying that the install is only enabled if you boot directly, which of course I can't do. Is there a way to turn the XP CD into a PXE-bootable image (like we did for WinPE)?
Did you solve this problem? I have the same problem(The "Install Windows XP" button is grayed out when I run setup.exe), anybody knows how to fix that?
Thanks
Client requested address 0.68.101.98 [06/06 04:53:16.643]
Suppress pingable address 0.68.101.98 [06/06 04:53:16.644]
Suppress pingable address 0.68.101.99 [06/06 04:53:16.647]
Suppress pingable address 0.68.101.100 [06/06 04:53:16.651]
Suppress pingable address 0.68.101.101 [06/06 04:53:16.655]
Suppress pingable address 0.68.101.102 [06/06 04:53:16.659]
Suppress pingable address 0.68.101.103 [06/06 04:53:16.666]
Suppress pingable address 0.68.101.104 [06/06 04:53:16.671]
Suppress pingable address 0.68.101.105 [06/06 04:53:16.676]
Suppress pingable address 0.68.101.106 [06/06 04:53:16.681]
Suppress pingable address 0.68.101.107 [06/06 04:53:16.691]
Suppress pingable address 0.68.101.109 [06/06 04:53:16.697]
then this repeatedly:
Client requested address 0.68.101.98 [06/06 04:37:27.658]
no more address or address previously allocated by another server [06/06 04:37:27.658]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:0E:7B:23:FA:11 [06/06 04:37:29.670]
Client requested address 0.68.101.98 [06/06 04:37:29.670]
no more address or address previously allocated by another server [06/06 04:37:29.670]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:0E:7B:23:FA:11 [06/06 04:37:33.679]
Client requested address 0.68.101.98 [06/06 04:37:33.679]
no more address or address previously allocated by another server [06/06 04:37:33.679]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:0E:7B:23:FA:11 [06/06 04:37:41.699]
...any ideas on how to get around this? I tried changing different settings in tftp32 but couldnt seem to let my m200 to access winpe.
if there is anyone out there :).
From this homepage:
http://home.allegiance.tv/~joem298/#restore
At step 5 which has the following content:
"The last file that you will need for your PXE server is a boot disk image. If you have a bootable floppy disk that you want to use for booting your M200, you can skip this step. Otherwise, find a blank floppy disk and insert it into your PXE server. Unzip the contents of 'BFD full package v1.0.7.zip' into a temporary directory. Open a command prompt and browse to that temporary folder. Run the command 'bfd msnet' in order to create the bootable floppy."
I dont have a floppy, I wont create a floppy.
How can I run the command bfd msnet?
Do I have to start cmd.exe? And then what do I have to type in? How can I browse to that temporary folder?
Questions over question....
Hopefully anyone can help me out there :|.
Greetings BeeDee
I solved my problem with the floppy. But I now have a problem on Step 3 on the other page of Deloy M200...
I will soon ask if i dont get any answer in the forum i asked for it.
Client requested address 0.68.101.98 [06/06 04:53:16.643]
Suppress pingable address 0.68.101.98 [06/06 04:53:16.644]
Suppress pingable address 0.68.101.99 [06/06 04:53:16.647]
Suppress pingable address 0.68.101.100 [06/06 04:53:16.651]
Suppress pingable address 0.68.101.101 [06/06 04:53:16.655]
Suppress pingable address 0.68.101.102 [06/06 04:53:16.659]
Suppress pingable address 0.68.101.103 [06/06 04:53:16.666]
Suppress pingable address 0.68.101.104 [06/06 04:53:16.671]
Suppress pingable address 0.68.101.105 [06/06 04:53:16.676]
Suppress pingable address 0.68.101.106 [06/06 04:53:16.681]
Suppress pingable address 0.68.101.107 [06/06 04:53:16.691]
Suppress pingable address 0.68.101.109 [06/06 04:53:16.697]
then this repeatedly:
Client requested address 0.68.101.98 [06/06 04:37:27.658]
no more address or address previously allocated by another server [06/06 04:37:27.658]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:0E:7B:23:FA:11 [06/06 04:37:29.670]
Client requested address 0.68.101.98 [06/06 04:37:29.670]
no more address or address previously allocated by another server [06/06 04:37:29.670]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:0E:7B:23:FA:11 [06/06 04:37:33.679]
Client requested address 0.68.101.98 [06/06 04:37:33.679]
no more address or address previously allocated by another server [06/06 04:37:33.679]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:0E:7B:23:FA:11 [06/06 04:37:41.699]
...any ideas on how to get around this?
Alex please let me know how you solved the problem?
driving me nuts!