Booting VirtualBox with USB workaround

Sorry, you shouldn't have created such a useful app! You have only yourself to blame!  

P.S. prefer the Start check option as the user may have changed the VM since he last ran VMS...?

P.S. prefer the Start check option as the user may have changed the VM since he last ran VMS...?

 

Could work but the problem is that I have to store somewhere the configuration of the last used VM. Only this way I can be really sure that it was changed or not. Because you can't count on the date of the file or the XML date; not even the checksum can't be used because maybe the user may just loaded the VM in VBM but without modifying the configuration - but VBM could still make some changes in the file..

 

LE: but if you want something just simple as you said it's doable:

 

 

How about if there is no VMS vmdk already in the VM (and you have requested a USB drive to be attached) then it warns you?

 

1.2 Beta 2 version

LE: link removed, you can find a better version in the next posts...

Changes:

Bugfix/Improvement: the code that checks again for vboxsvc.exe after killing was adapted to work on slower computers as well.
Improvement: if the VM doesn't have yet the VMSDrive***.vmdk attached and it finds other HDD's in the first positions in the storage controller(s) it warns the user it won't be able to boot from the first drive.

I think it looks a little better this way, isn't it...?

 

A small niggle - if the form does not have focus, then the selected VMS entry is not highlighted. This means I have to click on the form to select it first just to see what VMS is selected, and then click Start if the right one was already selected.

If I could see what VMS was selected when the form did not have focus, I could just click on Start straight away...

 

Also, personally, I would love a small column for the VT-x setting of each VM, this is because I usually have two VBox VMs, one with VT-x off and an identical one with VT-x on. This is because on my system, the stage 1 text mode install of XP crashes the VM if VT-x is enabled, but it runs OK (though slower) if VT-x is off. For stage 2 GUI-Mode and XP once installed, I run the VT-x ON VM as it is faster. I suppose this case is unique to me though...

looks cool + the suggestions from Steve = really cool

A small niggle - if the form does not have focus, then the selected VMS entry is not highlighted. This means I have to click on the form to select it first just to see what VMS is selected, and then click Start if the right one was already selected.

If I could see what VMS was selected when the form did not have focus, I could just click on Start straight away...

 

 

Yes, it does that but the problem comes partially from the window behavior in Windows and from the Win7 theme. When the window (of any application) loses focus the selection is painted with a less visible color. Unfortunately, on the default Win7 theme, it's almost the same with the color of the even numbered rows.
I can try to disable the default window behavior but it's not so easy and it's not recommended.
Or I can try to change the color of the even numbered rows so they look different from the selected row but still help the user; but if I increase the brightness they will not be distinguished from the background, if I decrease it it will start to annoy the user.

I will try to find a solution...

 

Also, personally, I would love a small column for the VT-x setting of each VM, this is because I usually have two VBox VMs, one with VT-x off and an identical one with VT-x on. This is because on my system, the stage 1 text mode install of XP crashes the VM if VT-x is enabled, but it runs OK (though slower) if VT-x is off. For stage 2 GUI-Mode and XP once installed, I run the VT-x ON VM as it is faster. I suppose this case is unique to me though...

 

 

A problem: this parameter does not have anything to do with adding/removing the real drives from a VM.
If in the future I will decide to show and even change other VM's parameters I will definitely have to change the interface.
I understand that it will help you a little but an easy solution is to create an entry for each of those 2 VMs in VMS and giving them suggestive names ("... VT-x off", "... VT-x on").

I will try to find a solution...

 

A problem: this parameter does not have anything to do with adding/removing the real drives from a VM.

If in the future I will decide to show and even change other VM's parameters I will definitely have to change the interface.
I understand that it will help you a little but an easy solution is to create an entry for each of those 2 VMs in VMS and giving them suggestive names ("... VT-x off", "... VT-x on").

Thanks!

and

That's what I do already  - no problem..it's just my usage is weird!

I have a solution for the selection problem: when VMS loses focus it will no longer paint the background of the even numbered rows. This way even the faint color of the selection will be still visible.

 

Focused:

 

 

Unfocused:

 

 

Is it ok...?

 

1.2 Beta 3 version

LE: link removed, you can find better version in the next posts..

Changes:

Improvement: "VM type" column replaced with icons.
Improvement: when the main window loses focus it will not change the background of even numbered entries.
Improvement: the background of the even numbered entries will be changed only if the number of entries is >= 5.

1.2 Beta 4 version

 Virtual machine starter GUI exe.zip   476.31KB   496 downloads

Changes:

Improvement: better icon for VB VMs.
Improvement: with Up/Down arrows you can cycle from the beginning of the list if you reached the end or from the end if you reached the beginning.
Bugfix: sometimes the icon of the VM was not showed.

If in a day or two nobody finds a bug or request an improvement, the next version will be the final version

If in a day or two nobody finds a bug or request an improvement, the next version will be the final version

what does that mean? are you getting bored with it now and saying you quit? I would like to test more but I cant do it in "a day or two" as I have another big project that is taking alot of time.

dont be in such a rush LOL its really cool what you are doing and I think it will take time for people to find and start using it but at some point I think it will be a popular tool.

slow down and keep perfect it.

Don't worry, I'm not bored and not in a rush but the thing is most of the users are usually waiting for the final version, because they consider the Beta versions unsafe. Partly they're right...

Ok, I will wait...

Oh, btw, have you solved the "dismount" problem...?

meant to say ...keep perfecting it in my previous post.


No, I didnt solve the dismount and that was where I left off. then I went to vmplayer and plop just to get a quick test in on a usb boot something that I was trying to figure out. sorry I can be more specific but I have been working on so many different things at once Im a bit scatter brained right now.

it started with trying to figure out how to get ewf working in XPx64 and now Im struggling with .VHD booting 7 because I dont want to install it for usage, I just want to reverse engineer the ewf components to try to get them working in XPx64. w7 is all new to me and I do not like one bit so far but in the last few days I went from complete novice to semi advanced user of 7 just trying to get a basic grip on the thing so I can pick up where they left off on XPx64.

at some point though I will be using your new tool a lot because I like Qemu and VB more than the others and I need the functionality that you are providing with this tool. it will take a while for me to get there though but when I do it looks like VMS will be one of the tools in my top drawer!

Im not sure that VMS is the best name though is it? I mean, it does that but it is more so USB tool I think. may need USB in the name, no? anyway.. keep up the great work! I think you are onto something.

Of course I will keep perfecting it. But from time to time I think that's wise to release final versions instead of a "forever Beta"...

A few days ago I tried VMS in Windows XP x64 SP2. It worked flawlessly.
In the error message about dismounting, VMS is also showing other informations, like "Possible reason:..." or "System message:...". What does it show on your computer?

Yes, "VMS" is not the best name but not the worst either. Somewhere in between...

I just dloaded your latest stable version so next time I boot up my XPx64 partition I'll try again and report back.

Steve, do you like surprises...?

urm... sometimes....

depends if it is a nice one or a nasty one!

1.2 Beta 5 version

 

LE: link removed, you can find a better version in the next posts...

Changes:

Improvement: just one but it's important. I will let you find what it is...

whoot , were.. a surprice ?? oh, i have hungry *bg* a chicken or an Turkey ?.. i have biiig hungry *bg*
or maybe a big familiypizzaaa ????
common, get the surprice.. *lol*    

 

 

 

edit :

uhm to late..

 

was only a programm, nothing to eat ! humm..

*very big grin*

 

edit 2:

thanks *bg*

 

best regards

Blacky

Edited by Blackcrack, 11 July 2013 - 03:05 PM.

     - great! Now I can leave VB Manager open all the time!

 

Thanks !!!! That is much much better!

 

Not to look a gift horse in the mouth, but does the VMS form have to disappear so soon after clicking 'Start' and ostensibly 'nothing happens' for about 10-15 seconds...

Could you not show some progress report on the form (or maybe a pop-up window) so we know what is happening. It would also be useful for problem reporting too, but the main thing is to provide some feedback to the user of what is going on before the VM actually runs. It would also help the user understand just what VMS does

 

e.g. progress reporting like...

checking VBox VM exists..OK

Adding USB drive 1 (WD Passprot 1.8TB)  to VM xxx.. OK

Adding USB drive 2 (USB 2GB) to VM xxxx.. OK

Checking if Vbox service is running.. OK

dismounting USB drive xxx..OK

dismounting USB drive yyy..OK

running VM xxx...OK

 

 

It would give the user more confidence when running the app for the first time.

 

P.S. Have a think about the name too. 'Virtual Machine Starter for USB drives'  or something like that??

now we need drivers for booting in usb for WinXP for automatical using the usb as normal storage ... Win7 should work in a usb easy

but i did not testing it now.. have here only 3x4Gig & 3x8gig Gig Sticks  therewith i mus use XP.. Win7 is too big..

but i don't have usb-stiorage drivers or how does it the PE Win XP ? With an USB-Storage too ?

 

it should prepare for booting over usb like an pe-System .. .. with usb-storage drivers ? how works it ?

 

best regards

Blacky

edit 2:

thanks *bg*

 

best regards

Blacky

 

You're welcome.

 

     - great! Now I can leave VB Manager open all the time!

 

Thanks !!!! That is much much better!

 

Not to look a gift horse in the mouth, but does the VMS form have to disappear so soon after clicking 'Start' and ostensibly 'nothing happens' for about 10-15 seconds...

Could you not show some progress report on the form (or maybe a pop-up window) so we know what is happening. It would also be useful for problem reporting too, but the main thing is to provide some feedback to the user of what is going on before the VM actually runs. It would also help the user understand just what VMS does

 

e.g. progress reporting like...

checking VBox VM exists..OK

Adding USB drive 1 (WD Passprot 1.8TB)  to VM xxx.. OK

Adding USB drive 2 (USB 2GB) to VM xxxx.. OK

Checking if Vbox service is running.. OK

dismounting USB drive xxx..OK

dismounting USB drive yyy..OK

running VM xxx...OK

 

 

It would give the user more confidence when running the app for the first time.

 

P.S. Have a think about the name too. 'Virtual Machine Starter for USB drives'  or something like that??

 

 

You're welcome.

 

On my computer the VM is loading in about 3..4 sec

Most of this time is VB loading the VM, so logging during this stage won't help much since I can't show how VB is loading its internal components...

But I will think about that.

 

Too long name... Maybe "VM starter for USB drives"... Although is not only for USB drives...