Multiple problems with RC1 on Mac Mini

Greetings, all.

I am having multiple problems with RC1 on my Mac mini that others may or may not be having, and wanted to make sure I posted about them so Parallels knew about them.

1- DHCP. Others seem to be having DHCP issues as well. Here is what I have determined:
-- Boot Mac. OS X gets IP address "A"
-- Boot Win2k in RC1. Win2k snags IP address "A" and forces OS X to grab IP address "B"
-- Reboot Win2k in RC1. Win2k snags IP address "B" and forces OS X to grab IP address "C"
-- the process continues as many times as I (re)boot Win2k in RC1

I am using bridged networking, just as I was in Beta 4 and Beta 6.

2- Speed. Parallels shows that VT-x is enabled (About Parallels Desktop says Virtualization Mode is "Intel VT-x" and Remote Session is "Off"), but my system slows to a crawl. Windows seems to run about as fast as it used to, but OS X is terribly slow now. System is a core duo mini with 1GB RAM, and 2 users logged in - exact same configuration I had with Beta 4 and Beta 6, but system response is MUCH worse in RC1.

Neither of these issues was a problem in Beta 4 or Beta 6. To get around issue #1, I renumbered my home network such that everything except my laptop uses static configuration. This wasn't very fun to do. To get around issue #2, I have been using Parallels Desktop less and less, which also isn't something I want to do. I bought Parallels Desktop to use it, not to just have it installed.

Any tips on resolving these issues would be most appreciated.

 

Could you check both issues in new RC2 please?

 

Sure. I didn't see a RC2 when I went to look for one this morning. I'll try that and get back to you. Thanks!

 

You guys rock! Both of those issues are resolved in RC2 - thanks!

But another issue - one I forgot to mention - persists. It has existed since I started using Parallels Desktop/Workstation, which was with Beta4.

I have a USB-serial adapter that works fine in Windows and works fine in OS X. It works with Parallels, but only as long as its driver (by FTDI) is not installed in OS X. This means that I can only use the USB-serial device in OS X (with driver installed in OS X), or in Windows (without driver installed in OS X).

With the driver not installed in OS X, it connects to the VM instantly, and Windows sees it as COM3 or something. With the driver installed in OS X, upon connecting the USB-serial device I get the usual mssage that the device is in use by another process, that I should wait 5-10 seconds and then retry manually. No matter how long I wait or how many times I try, it will not connect to the VM if the OS X driver is installed.

I know you guys are still working on USB connectivity, but it might be worth noting that on my G4 PowerBook, I can use the device on OS X and on Windows (through Virtual PC).