The fix in 2.0.1 was to the particual problem of when if you attached the
a DOS partition you could get a "VM_DIED". The VM_DIED just means that
something did something illegal in the virtual machine, and it had to
be killed. Basically anthing that would kill or lockup a normal Windows
machine results in a VM_DIED. There have been bugs in Win4Lin that result
in this, and still might be more, but a funky installation of Windows
can also be the problem. Such as something bad in the registry or a
misbehaving application, or corrupted files.
There are some things that can be done to try and narrow down the possiblities
Is there anything in the file $HOME/.merge/em.log ?
If so, sometimes it as a hint about the problem.
(Note: The contents of this file are pretty cryptic!)
One thing to do if you have enough disk space is to move your $HOME/win
directory aside and do a reinstall of Windows. E.g.
cd $HOME
mv win win-old
winsetup
(use winsetup to "save as" the win configuration as "win-old"
and then change the win-old configuration to have the C drive
specification to point to $HOME/win-old.
Now you can then access the old installatioin with "win +kwin-old" (or fwin +kwin-old),
and if you run just "win", it will let you install Windows into a new $HOME/win
directory. This way you can experiment with a working and non-working Windows
installation to see what might have caused the problem. You can also do this
before you have a problem, to try out potentially dangerous things in a separate
sandbox.
Other things that can be done to diagnose a problem is to get a "dos log.
This is a log file which shows what file related transactions have happened.
This log file is also fairly cryptic, but can be helpful for an experienced
dos log reader.
The typical way to get a dos log is to use this command to start up your session:
DOS_LOG= win &
This creates the log file $HOME/dos.log
Note that doing this can slow down your file access, and result in a very
large file.
-David
Peter Ruskin wrote:
>
> OK, I read the announcement on the web page, that claimed that 2.0.2 fixed
> the "VM_DIED" bug, so I downloaded it and upgraded.
>
> Guess what - if I use the command `dos &`, I get a window that I can't
> type into - it dies after a few seconds with "VM_DIED".
>
> I'm still waiting for kernel 2.4.0 support. Win4Lin 3 is expected "in the
> spring" (of 2001?), which starts here in six days time. Wonder if that
> will support 2.4.0?
>
> I'm starting to wonder why I spent money on this product.
> --
> ----------------------------------------------------
> Linux Mandrake release 7.2 (Odyssey) for i586
> KDE 2.1
> Linux 2.2.17-27mdkWin4Lin, Uptime 7 hours 50 minutes
> ----------------------------------------------------
> _______________________________________________
> Win4Lin-beta mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-beta
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
