It's with xterm. When i double-click on the Router, this is the window of the VM who bring to front.

Some suggestions/requests.

Please add Virtual PC icon in the bar, can be very useful.

Why VBOX stations starts connection from ethernet 1 NOT 0 ????
Now I must manually change all my best topos reagarding this NEW VBOX opion:(.
Beta version has not this option, all VBOX starts from e0,

why and for what request it has been added??
Is it possible to change that my VBOX starts from e0 ????

Technologov maybe You know??

Hi,



For VPCS you mean? I have plans to integrate vpcs directly in Dynamips.



The problem of starting at e0 is that doesn't match with Vbox interface naming that starts at 1. Also you have the first Vbox interface reserved for your VM to access the host (your OS), this has been done by design when Technologov developed Vbox support. Therefore, the first usable interface in GNS3 is e2 corresponding to interface 2 in Vbox or eth1 in Vbox guest Linux VMs.

I know this can be problematic for some scenarios and I would like to change that in future releases. At least give users an option to use the first Vbox interface (not having access to the host). If you have an idea how to handle interface naming with the least confusion, please tell me :)

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.

For VPCS you mean? I have plans to integrate vpcs directly in Dynamips.

I mean just icon (button) on taskbar what calls out VPCS console, thats it:). Otherwise I need go to start->GNS3->VPCS.

Just button what calls out VPCS console window.

Jeremy,
One more question.
I got problems with memory amount for Dynamips hypervisor. Previous (beta) I had 2048, and everything works fine.
Now in tests I leave 2048 on that, and all topos crashes on 8th or 7th router... starts.

It has been solved when I changed from 2048 to 1024.
Strange.

Uldis

Might not be an issue anymore since I'm still on the BETA.. but i'll mention it anyways ;)

With the BETA on Snow Leopard.

Adding and removing virtual network cables is not updated until a reboot of the vm's.