-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello again.
Like the subject says, the problem of not being able to start my vm after upgrading to vbox 1.5 has been solved. I won't describe what I did to figure things out, but it was adding the serial port to the vm that was causing the problem, and I guess it could be classified as user error, (I.E., the issue wasn't being caused by the serial code in vbox). There is a program that I use, which uses com2, whenever its icon is accessed from my computer/windows explorer. Since I had neither of these opened at the time, I assumed that com2 was free, but as I just found out, this program keeps com2 open for itself, even if I'm not using it via my computer/windows explorer. The system freeze problem wasn't specific to vbox either, the same thing happened when I tried using hyper terminal on com2. In a nutshell, please disregard my previous post, the problem is solved, and everything works just fine. Again, a very, very big thank you to the person who added host serial port support. Greg - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG3JXF7s9z/XlyUyARAqTrAJ4if7L+lDfKnV4XZ5L50Rc29MEkWACffFz+ yLF0hFPahr7SCWIdmeKWXiQ= =cBUD -----END PGP SIGNATURE----- _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
