On 15 Mar 2001 12:01:11 -0500, [EMAIL PROTECTED] wrote: > Send Win4Lin-users mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.netraverse.com/mailman/listinfo/win4lin-users > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Win4Lin-users digest..." > > > This is the Win4Lin-users mailing list Digest. When replying, please change your >subject heading to match the individual message you're replying to, instead of >"Win4Lin-users Digest". > > Today's Topics: > > 1. aborts with sound? (Dan Swartzendruber) > 2. Re: aborts with sound? (yan seiner) > 3. Win4Lin 2.0.2 bugfix doesn't (Peter Ruskin) > 4. Sound with WIN4LIN? (Vlad) > 5. Re: Sound with WIN4LIN? (Vlad) > 6. Re: Win4Lin 2.0.2 bugfix doesn't (David Peet) > 7. trailing garbage when moving window in win4lin (Jinwei Shen) > > --__--__-- > > Message: 1 > To: [EMAIL PROTECTED] > Date: Wed, 14 Mar 2001 19:14:04 -0500 (EST) > From: [EMAIL PROTECTED] (Dan Swartzendruber) > Subject: [Win4Lin-users] aborts with sound? > Reply-To: [EMAIL PROTECTED] > > > i just started (a couple of days ago) listening to mp3s in linux, while running >win4lin (which is configured to use the sound driver as well). i did this because >the sound was cleaner than under win4lin. i've noticed that win4lin will not run >more than a few minutes with an mp3 running in the background (under linux). the >screen will suddenly freeze up, and then the session dies (with no apparent error >message). i'm assuming this is some kind of sound driver conflict, but if so, what >is the best way to deal with this? > > > --__--__-- > > Message: 2 > Date: Wed, 14 Mar 2001 19:23:50 -0500 > From: yan seiner <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [Win4Lin-users] aborts with sound? > Reply-To: [EMAIL PROTECTED] > > I just started noticing this on a Toshiba laptop, with a yamaha 754 sound card. >First, there is minor corruption of the video - some pixels turn black. Then the >screen freezes. Or sometimes the system just locks up. Sometimes all is fine. > > Other systems work fine. > > I'm guessing it's some interference between the alsa modules and the merge modules. >I have not found any pattern to this; the problem does not manifest if the sound >modules are not loaded. > > --Yan > > Dan Swartzendruber wrote: > > > i just started (a couple of days ago) listening to mp3s in linux, while running >win4lin (which is configured to use the sound driver as well). i did this because >the sound was cleaner than under win4lin. i've noticed that win4lin will not run >more than a few minutes with an mp3 running in the background (under linux). the >screen will suddenly freeze up, and then the session dies (with no apparent error >message). i'm assuming this is some kind of sound driver conflict, but if so, what >is the best way to deal with this? > > > > _______________________________________________ > > Win4Lin-users mailing list > > [EMAIL PROTECTED] > > https://lists.netraverse.com/mailman/listinfo/win4lin-users > > > --__--__-- > > Message: 3 > From: Peter Ruskin <[EMAIL PROTECTED]> > Organization: none > To: [EMAIL PROTECTED] > Date: Thu, 15 Mar 2001 02:18:24 +0000 > Cc: [EMAIL PROTECTED] > Subject: [Win4Lin-users] Win4Lin 2.0.2 bugfix doesn't > Reply-To: [EMAIL PROTECTED] > > 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 > ---------------------------------------------------- > > --__--__-- > > Message: 4 > Date: Thu, 15 Mar 2001 00:47:05 -0500 > From: Vlad <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [Win4Lin-users] Sound with WIN4LIN? > Reply-To: [EMAIL PROTECTED] > > Re, > > is Sound Blaster Live is ALSA (Advanced Linux Sound Architecture), hence > will not work under win4lin? if im wrong and anyoen got the card working.. > please let me know. > > - -- > tmd > > --__--__-- > > Message: 5 > Date: Thu, 15 Mar 2001 02:48:07 -0500 > From: Vlad <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [Win4Lin-users] Sound with WIN4LIN? > Reply-To: [EMAIL PROTECTED] > > Nevermind me.. got it working :) > > On Thu, Mar 15, 2001 at 12:47:05AM -0500, Vlad ([EMAIL PROTECTED]) wrote: > > Re, > > > > is Sound Blaster Live is ALSA (Advanced Linux Sound Architecture), hence > > will not work under win4lin? if im wrong and anyoen got the card working.. > > please let me know. > > > > - -- > > tmd > > _______________________________________________ > > Win4Lin-users mailing list > > [EMAIL PROTECTED] > > https://lists.netraverse.com/mailman/listinfo/win4lin-users > > -- > - -- > tmd > > --__--__-- > > Message: 6 > Date: Thu, 15 Mar 2001 02:16:55 -0800 > From: David Peet <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED] > Subject: [Win4Lin-users] Re: Win4Lin 2.0.2 bugfix doesn't > Reply-To: [EMAIL PROTECTED] > > 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 > > --__--__-- > > Message: 7 > To: [EMAIL PROTECTED] > From: Jinwei Shen <[EMAIL PROTECTED]> > Date: 15 Mar 2001 11:45:30 -0500 > Subject: [Win4Lin-users] trailing garbage when moving window in win4lin > Reply-To: [EMAIL PROTECTED] > > I installed win4lin 2.0 in a upgraded redhat-6.0 box. When i try to > move windows in win4lin, there left trailing garbage in the screen. I > can use Refresh to remove the "garbage" on the background, but the > moved window contents also got corrupted. > > This does not happen when I remotely run the same win4lin installation > on another machine. So, I am guessing this maybe a XFree86 server > problem. The machine with problem uses a nvidia 128 video card, and > XFree86-SVGA-3.3.6-20 server. I also tried different combination of > screen resolution and color depth, and this does not solve the problem > either. > > Helps? > > -- > Shen > > > > --__--__-- > > _______________________________________________ > Win4Lin-users mailing list > [EMAIL PROTECTED] > https://lists.netraverse.com/mailman/listinfo/win4lin-users > > > End of Win4Lin-users Digest > _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
