Local LivePC shows up as "Not Buffered"
Submitted by mister red tape on November 1, 2006 - 10:57am.
Using LivePC installed to USB disk. Installed it while connected to home PC (it showed up as I drive there).
Bring it to the office (where it is E drive) and:
* The disk looks like it is constantly being accessed
* VMWare network setup constantly pops up and copies some files or does some config thing
* LivePC installed ON THE DRIVE shows up as "not buffered" (Why is it even being buffered??)
* When I start LivePC it will warn me that it's slow because it's not buffered... whatever
* When VMPlayer starts, it says it's not properly configured and shuts it down!
I have installed LivePC to the USB disk from my work laptop before and it hasn't tried to buffer a local installation. Everything works.
What is the problem? Is it only supposed to work off one computer?
Temporary fix
Submitted by mister red tape on November 1, 2006 - 3:24pm.
This can be fixed (for now) by downloading USBDLM from here:
http://www.uwe-sieber.de/usbdlm_e.html#problems
Assign a particular letter to your USB drive by putting USBDLM.ini in the root of the drive and specifying
[DriveLetters]
Letter1=V
(at least that's what I do). Do this on computers you want to use the drive on...
Ignore if your USB drive ends up being E or something everywhere you go, but I would suspect that's not the case. I have differing numbers of drives on my different systems, so...
Since moka5 requires admin rights to run anyway, there are bigger problems at hand for portability.
Sorry you are having
Submitted by John Whaley on November 1, 2006 - 7:49pm.
Sorry you are having problems. The problems of showing up as "not buffered" when you change drive letters and the warning on startup are fixed in the next release (Beta 6), which will be out Real Soon Now. The error on startup is a little more disconcerting. If you send us the m5engine.log file, located at E:\moka5\Documents and Settings\moka5User\Application Data\moka5\Engine\m5engine.log, we should be able to diagnose what is going on.
Also it would be helpful if you can provide the the vmware.log, the vm.vmx and the vm.xml for this LivePC so we can check it out. Please send the info to [email protected]. The files will be in the following path on your USB drive: E:\moka5\Documents and Settings\moka5User\Application Data\moka5\Engine\[LivePC Name]\activation
Again, sorry for the problems and we hope you'll stick with it as we iron out the issues in the beta.
-John
Good to know
Submitted by mister red tape on November 1, 2006 - 10:54pm.
So the Vmware player message pops up only when it is having the buffering issue. So it never fully buffers the livepc up anyway, right? So if you start it (all the while another window keeps trying to copy vmware networking files over), the Vmware player complains that it is not set up properly.
If you've fixed the bug do you think you probably resolved the other one too?
I will try and duplicate it for you.
Meanwhile, I am having good luck pointing the USB drive to a single letter using USBDLM.
Looking forward to Beta6.
This will happen if the USB
This will happen if the USB drive sees itself assigned a different letter than what it saw when the livepc program (or a particular livepc) was installed.
It defeats the purpose of carrying this thing around and using it on different systems...