Latest version of virtualBox script?
#1
Posted 21 February 2010 - 06:53 AM
there are several version of the virtualbox script and for me no version really worked with current virtualbox versions...
can anyone recommend which version to use an is there one that actually works with latest VB version?
thanks !
#2
Posted 21 February 2010 - 07:45 AM
I guess vbox added-removed something again, vbox 314 complains about medium here...
#3
Posted 21 February 2010 - 08:17 AM
it does not work when the project name has a space in the name...
some quotes need to added...
Peter? My script is certified by you...
#4
Posted 21 February 2010 - 08:20 AM
i am not familiar with VB and so maybe someone could help a bit...
#5
Posted 21 February 2010 - 08:24 AM
Peter? My script is certified by you...
Certification is about server maintance, nothing special for script
Check here
http://www.boot-land...?showtopic=8866
ps: I will install 3.1.0 to see how current scripts work, coming soon
#6
Posted 21 February 2010 - 08:55 AM
#7
Posted 21 February 2010 - 10:38 AM
I made a set of tests with different versions of vbox (3.04 to 3.14) with different vbox script... failed. (truely I made tests as a side-task for my test builds..)
Honestly, I like vbox a lot, but not the scripts of it . Sorry I do not have time to fix scripts (which I am posponing for a long while now because of other things....)
At least I tried
For others, here is latest vbox script
http://nativeex.boot...rtualBox.script
Since most projects (including LiveXP) use %Isofile% variable,
start replacing %BurnISO% with %Isofile% inside the script
Than Happy time for fixing.
#8
Posted 21 February 2010 - 10:55 AM
#9
Posted 21 February 2010 - 06:37 PM
Since most projects (including LiveXP) use %Isofile% variable,
start replacing %BurnISO% with %Isofile% inside the script
Better would be to adapt your project to use %BurnISO% (Search in nativeEx_Win7 for it).
Then you can use newer versions as original.
Peter
#10
Posted 21 February 2010 - 07:17 PM
here at post 38
http://www.boot-land...?...ost&p=88220
you asked me to prepare a solution (we contacted about %ISOFile% usage, you than understand it is similar to %BurnISO% you use but it has more advantages, follow ++)
so I change rest of livexp finish scripts to use %ISOFile% as a variable for finish scripts (image creation+emulator+cd writer).
++It is verrrrry practical (anyone can easly understand and use)
++Fully compatible with any future project and new project (since any project start with establishing %ISOFile% which is a natural wb variable)
++Currently now LiveXP can easly share finish scripts with any other PE2/3 projects that exists.
++And in future it is now very easy to add more finish scripts.
#11
Posted 21 February 2010 - 07:21 PM
The problem is with newer VB version only and burniso has nothing to do with it
Already fixed it and a new script will be posted here (maybe tomorrow...)
Sorry, but burniso does not sound like a good idea to me...
#12
Posted 21 February 2010 - 07:41 PM
%BurnISO% is what you finally burn to CD or copy to USB or try in emulator,Sorry, but burniso does not sound like a good idea to me...
independent of all the ISOFiles or RAMISOFiles or ???ISOFiles you have used during the build.
Peter
#13
Posted 21 February 2010 - 08:11 PM
Looking forward to itAlready fixed it and a new script will be posted here (maybe tomorrow...)
and if you take request, may i ask ac97 support
here is an old modified script from Kare that he said (that time) including ac97 support
http://lancelot.winb...ualBox_kare.rar
#14
Posted 22 February 2010 - 09:56 AM
#15
Posted 22 February 2010 - 11:13 AM
@amalux: in case you are also working on a vb script to boot the pe in vb 3.x please tell me so i do not have to spend time on this...thanks !
#16
Posted 22 February 2010 - 07:03 PM
Hi ctmagyes, but you (as myself) made the mistake to not read correctly...the script is for running vb inside your pe.-))
@amalux: in case you are also working on a vb script to boot the pe in vb 3.x please tell me so i do not have to spend time on this...thanks !
I've read this 5x and give up, what is it you're trying to do? Booting PE in VBox 3.x (running on host or in PE) is as simple as could be so I'm sure I'm mis-understanding you. Please re-state your needs.
#17
Posted 22 February 2010 - 07:18 PM
If i saw it right, your new script allows the use of VB inside a booted PE. This is not what i was talking about, i was talking about booting an ISO after it was made by WB to test the resulting PE.
The current VB script (not yours, the one included in the projects) for booting the %isofile% (generated by a project, no matter if LiveXP or Win7PE or whatever) does not work with current VirtualBox versions...the VB syntax changed quite a bit...
I will make a new VB script as soon as time permits...i was thinking, maybe you are making one already, i just don't want to do something that is already done...
Hope this clears it up.-)
#18
Posted 22 February 2010 - 07:46 PM
setiso.png 42.62KB 4 downloads
#19
Posted 22 February 2010 - 09:01 PM
Why do you not use established VirtualBox versions lke 3.1.2 to ONLY EMULATE your ISO?
If you have some reasonable explanation, please tell us.
If you do not have an explanation besides "I always need the latest version, independent of it gives some troubles to my installation", forget it and bring your emulation to run.
I prefer a use of the version which ios e.g. included in native>Ex_barebone or nativeEx_Win7. THis version is sure to run well with the project.
Peter
#20
Posted 22 February 2010 - 09:19 PM
BTW: can you explain what the wrapper does? I found no need to use it...at least not with 3.1.4
#21
Posted 22 February 2010 - 09:36 PM
Sorry: My VirtualBox.script version 033 works with currently 3.1.2 in ALL nativeEx projects.sorry, your versions did not work with any 3.x version i tried, and so i decided to make the latest work...thats all...
BTW: can you explain what the wrapper does? I found no need to use it...at least not with 3.1.4
If you want to try in a different project, you MUST ADAPT something like %ISOFile%, %BurnISO% etc.
BTW: I'm currently working on "Making %BurnISo% and %Isifile% obsolete for dummies"
BTW2: Because I could not install / bring to run 3.1.4 on my host, I'll NOT adapt the script to use it.
Peter
#22
Posted 22 February 2010 - 09:50 PM
It would be more easy to adabt nativeex projects use %ISOFile% variable like allllll others (and natively winbuilder does). Here we have 3 finish scripts creating 3 different named files (LiveXP.iso , LiveXP_Ram.iso , LiveXP_Wim.iso) (number will be 4 to 6 in some time) without any problem on emulator and iso burning scripts.BTW: I'm currently working on "Making %BurnISo% and %Isifile% obsolete for dummies"
As i wrote before, it would very easy (dummiest ever) for me to use ctmag script on livexp, just copy & paste. I guess ctmag can also use other scripts of livexp (vmware, imgburn and maybe qemu) on his project by only copy & paste.
why don't you like copy & paste.
#23
Posted 22 February 2010 - 10:04 PM
Inside a project there are many possible different files like '%RAM_ISO%' or similar.
They sometimes appear as %ISOFile%.
%BurnISO% is what is burned to CD, but also what is copied onto USB or is used as boot image for the emulator, or ...
That was the reason I made nativeEX for 100% clean and related everything to %BurnISO% and brought the old %ISOFile%, %RAM_ISOFile% etc. stuff to background.
Nobody is forced to use my way.
It is only a suggestion, I realized for nativeEx_barebone and nativeEx_Win7, and we do not have to discuss for different projects.
If you do not agree, simply forget it. Maybe your way works in your project ...
Issue closed for me.
Peter
#24
Posted 22 February 2010 - 10:19 PM
and I already explained in different place same tasks can already be done by using %ISOFile%, %100 clean.I already explained at a different place:
This is not my special way, this is the way all projects use (except 1)If you do not agree, simply forget it. Maybe your way works in your project ...
Sure. But for this specific case it is not polite to use special variables. Remember, it took a long while to convince other projects use common variables like %GlobalTemp% , %GlobalSupport% etc.Nobody is forced to use my way.
Anyway, it seems this is another endless loop.
From current topic experience, it will be nicer if you decide easly compatible (with your words: "obsolete for dummies") scripts so dummy community can use your scripts for emulator tasks easly.
For other project than nativeex, "dummiest ever" method of copy&paste will continue working for emulator scripts .
As a result everybody (all dummies) happy.
#25
Posted 22 February 2010 - 11:02 PM
Anyway, it seems this is another endless loop.
For me it is ended. I declared discussion for me closed last post.
Peter
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users