Win4Lin provides access to the Linux filesystem, so there
is no underlying DOS block filesystem. So any tools that
operate directly with the low-level DOS filesystem,
such as the "block level" stuff or muck around in the
FAT tables cannot work with drive that provide access to
Linux files.
You can attach the DOS partition if you want, and then
a real DOS filesystem will be there and the Windows/DOS
drivers are used to operate on it at the block level.
Windows itself has a method for restoring registries.
This is from the help for regedit:
To restore the registry
Click Start, and then click Shut Down.
Click Restart in MS-DOS mode, and then click Yes.
At the MS-DOS prompt, type
scanreg /restore
Restart your computer.
Note
Following this procedure will restore your registry to
its state when you last successfully started your computer.
I actually have not tried this. What you do with Win4Lin is
start a dos sesson this way:
dos +w
And then at the C> prompt type the command, and then type "quit"
and then try starting you Windows session again (i.e. "win &").
Also because Linux is available before (as well as during) the
Windows session you can make backups (and do restores) using
Linux tools. For example:
1: Make a full copy of your C drive (e.g. $HOME/win)
(Do this before your C drive is messed up :-)
For example:
cd $HOME
mkdir full-backup-win
cd win
find . -depth -print | cpio -pdm ../full-backup-win
date > ../full-backup-win/timestamp
This gives you an easy copy of all the files on the C drive.
Or to save space you could keep the backup as a gziped archive.
2: Use your own script to start a Windows session that
first makes a backup of the files that have changed
since the last backup. You could have this do an
incremental type backup, which each incremental having
the changes since the last incremental, or make it
easy (and usually slower) to back up everthing since
the last full backup.
For example to save the changes since the last full backup
(as in the example in #1 above):
cd $HOME/win
find . -newer $HOME/full-backup-win/timestamp \
| cpio -o | gzip > $HOME/inc-backup.$$.cpio.gz
win &
With this example you would want to periodically remove
older the incrementals that are not needed anymore.
-David
Dan Swartzendruber wrote:
>
> does anyone have a preferred windows tool to allow backing out of
> recent "bad idea" changes? one that i had used under native win98
> and win98/vmware is a package call GoBack, that hooks into the disk
> driver. you can go back to timestamped snapshots and it will do a
> block level recovery. very nice. unfortunately, it doesn't work
> under win4lin, since it thinks that win4lin is providing a driver
> which isn't compliant in some respect or another. i also tried
> norton 2001, but that left my system unusable (fortunately i had
> backed up the ~/win directory).
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
