How to create easily a second Win98/XP in the same computer. using Windows 98 to clone, maintain, repair and rebuild Windows XP.
Posted 12 January 2009 - 07:48 PM
Excellent info on your pages! Also found this -
which acknowledges and links to your work.
Between you and them (among others), I have finally figured out how to transfer my old PC to my new PC ( multi-booting, of course ). Still a work-in-progress, but well on the way now, with your help!
And Welcome to the Fray!!!!
Posted 13 January 2009 - 01:27 PM
Unless you use Letter Assigner :
Homepage is no more:
but can still be found on the Wayback Machine:
Posted 16 January 2009 - 01:50 AM
In 98SE2ME options 1 + 2:
To backup Windows 98 SE I use a DOS style batch file [CLONE98.BAT] and the DOS based tool XCLONE.EXE [free] which backs up the entire %windir% [usually C:\WINDOWS] folder + all subfolders + all files to any destination [requires editing the BAT] with 1 click.
Details here [the "BACKUP + RESTORE WINDOWS 98 SE" + "TESTING... CLONE98.PIF + 98RESTOR.BAT" sections]:
To restore Windows 98 SE from the backup [created by CLONE98.BAT] I use 98RESTOR.BAT which uses Win98SE's own MOVE.EXE native DOS mode tool.
These 2 BAT files must be executed from within Windows.
Some of these backup/restore operations require re-booting to native DOS mode.
Posted 07 February 2009 - 06:51 AM
Why not on it's homepage?
A few (needed in my view) corrections you may want to consider:
BOOTPART WIN98 BOOT:C:
This WON'T affect the MBR, it will only replace the CODE of the bootsector, previously set to the XP one that invokes NTLDR, to the Win98/DOS one that invokes IO.SYS.
BOOTPART WINNT BOOT:C:
BOOTPART WINNT BOOT:C:
Though in this specific context it doesn't make a difference, you should "make your mind" about using WINNT or WINXP parameter.
Just for the record, and this is not at all a critic to your post , the method you describe is a bit "old-style" .
BOOTPART.EXE was born more than 15 years ago, and while at the time there were no alternatives, today using grub4dos and it's feature of directly chainloading system files, it is not necessary to fiddle with bootsectors.
Posted 07 February 2009 - 11:15 AM
I've also rectified the download adress.
This is the way I knew and so is how I did it. Well, in fact the essential thing is that it works perfect. But it is always good to know that there are better ways for doing things. I like learning.
Thank you for your help, jaclaz!
This post has been edited by cannie: 07 February 2009 - 11:49 AM
Posted 07 February 2009 - 01:55 PM
The point was that bootpart does NOT touch the MBR (Master Boot Record), it changes the PBR (Partition Boot Record) or bootsector.
The MBR is first sector of the whole hard disk or PHYSICAL DRIVE, CHS 0/0/1, LBA 1
The PBR is first sector of the active partition, usually first one, first sector of LOGICAL DRIVE, usually CHS 0/1/1, LBA 64.
You are welcome, just trying to avoid possible misunderstandings of less experienced users.
Posted 07 February 2009 - 07:52 PM
Thanks, jaclaz! I always learn something new by reading your posts!
Posted 08 February 2009 - 04:07 AM
I'll surprise you with yet a new notion :
(Extended Master Boot Record)
(Extended Partition Boot Record):
Posted 08 February 2009 - 09:01 AM
Yes we could , it would be more accurate, though I have already seen the term "main" as used instead of "primary", as they are synonyms:
In any case it won't change the sense of the tutorial, the distinction between "main" (or "primary") and "logical unit of the extended partition" is clear enough , while exchanging MBR with bootsector appears as more confusing, and particularly on a topic where a lot of people appear to have not a deep enough knowledge.
even the good MS guys sometimes happen to add to the confusion:
that misrepresents at first sight what bootsect.exe does, using the terms "master boot code" for the bootsector code: Bootsect Command-Line Options
Bootsect.exe updates the master boot code for hard disk partitions to switch between BOOTMGR and NTLDR. You can use this tool to restore the boot sector on your computer. This tool replaces FixFAT and FixNTFS.
Though accurate in the sense that it makes the distinction between the "boot code part" (which is changed by bootsect.exe) and the "volume data" (which is left unchanged by bootsect.exe) using the "master" adjective to describe the "boot code" probably creates the misunderstanding.
Posted 08 February 2009 - 09:44 AM
It is commonly said "Four eyes see more than two". In this case there are more than four.
I also added something concerning disk maintenance at the end of the post.
IMHO the important thing is making the tutorial useful for anyone who needs it.
Any other improvement will be welcome.
Thank you very much.
This post has been edited by cannie: 08 February 2009 - 10:09 AM
Posted 08 February 2009 - 01:39 PM
Posted 09 February 2009 - 02:18 AM
It is clear that infalibility is not my strong point. I've rectified it.
Thanks again, jaclaz.
Posted 14 February 2009 - 01:12 PM
To make it easier for newbies I decided to put all together in the first post.
If moderators believe it should be placed anywhere else, please post it here.
Thanks to you all.
Posted 04 March 2009 - 06:25 AM
Posted 14 March 2009 - 01:49 PM
Please note that FDISK /MBR only replaces the MBR CODE (with the "default" Win9x one).
It does NOTHING if the Virus or whatever has corrupted the MBR DATA.
It is always a good idea to have (possibly on the same "emergency floppy" a backup of the complete MBR.
If you don't have it, your only way out (possibly) is the use of TESTDISK:
to re-build the MBR DATA
It is unclear/undocumented if there is any advantage (or drawback) on a dual boot system to have the Win9x MBR CODE or the 2K/XP/2003 one.
BOOTPART WINXP BOOT:C:
BOOTPART WIN98 C:\BOOTSECT.W98 "Windows 98"
Later on, when the system is already operating normally, the created Msdos.sys must be replaced by the one at the Windows 98 boot floppy and the boot.ini must be edited because Windows 98 appears twice to eliminate the second one.
Not really. :whistling:
If you already have an entry for BOOTSECT.W98 in your BOOT.INI you can simply run:
BOOTPART WIN98 C:\BOOTSECT.W98
a new bootsector will be created, but NO entry will be added to BOOT.INI.
Of course you need to use the SAME "BOOTSECT.W98" name for the "old" and the "new" bootsector.