55 replies to this topic

[pscEx]

Sorry: My VirtualBox.script version 033 works with currently 3.1.2 in ALL nativeEx projects.

BTW2: Because I could not install / bring to run 3.1.4 on my host, I'll NOT adapt the script to use it.

I now installed 3.1.4, and it worked w/o changing anything in the script.

I made a new script version having the download link to 3.1.4

Peter

[pscEx]

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.

If you decide to insert one line into the makeISO script:

Set,%BurnISO%,%ISOFile%,PERMANENT

you can use EVERY emulator from nativeEx project.

Peter

[pecd.net]

hmm, i will try the script again...but still i need some cahnges...we will see...

[Lancelot]

If you decide to insert one line into the makeISO script:

Set,%BurnISO%,%ISOFile%,PERMANENT

you can use EVERY emulator from nativeEx project.

as written before, with new version I still get "Could not read from the boot medium! System halted" with LiveXP (even with the changes you suggested).

vbox 314 complains about medium here...

and as written before, I am sure new (and old) script works in nativeex world.

[pscEx]

I think that I already explained to you in ICQ:
Look into VBox project's setup
 vbox.gif   32.08KB   12 downloads
When you see the "Guest Additions", somebody has tried to add these additions from inside a PE in emulator.
VirtualBox now on next boot wants to boot from the "Guest Additions", and thats unfortunatelly not bootable.

How to fix: Just remove this virtual CD from the configuration.

My VirtualBox does not try to delete ANY of the CDs, HDDs etc for the PE. They may be added by the user.

But I can try to delete a VBoxGuestAdditions.iso, if found.

Peter

[pecd.net]

@peter:

may i ask again: what does vboxmanwrap.exe do?

i found this text in the exe and this lete sme assume you wrote it...

WinBuilder .script interpreter designed for bootable media

[Lancelot]

I think that I already explained to you in ICQ:

omg, now I understand

so outofbox vbox is not usable by scripts !!

I will test and check tomorrow

[pscEx]

@peter:

may i ask again: what does vboxmanwrap.exe do?

i found this text in the exe and this lete sme assume you wrote it...

WinBuilder .script interpreter designed for bootable media

You add a CD to VBox using VBoxManage.exe with "registerimage <isofile>".
That is done well, but from now on this image is registered under a GUID.

The next trial wants to register the ISO. But VBox says that it already knows this name, and refuses to register.
Therefore, before registering a ISO from WB, you must unregister the old one.

But unfortunatelly (at least until now, maybe in 3.1.4 it is possible) you cannot unregister using <isofile>.
You have to use the GUID.
But in WB you do not know the GUID which is generated for your CD.

Query for GUID etc. is done by VBoxManageWrap.exe

Peter

BTW: When you look into my previous post: I want to try here to unregister Guest Additions.

[pecd.net]

Thanks for explaining...

It looks like the only thing still missing is sound support for lancelot...maybe you are willing to add this as an option?

[pscEx]

[Lancelot]

As I wrote mannnnny times before (and even before this topic): I freshly installed vbox, never tried to add "Guest Additions" , livexp could never boot.

I decide to check the script, and found, script has a bug.

Where I was mistaken: I trusted psc preparing nativeex scripts fully compatible to any folder (and name related things), as a result I never thought there would be a bug related to this.

Where psc was mistaken: Ignored the report.

How to fix: No need to, I already fixed and uploaded to LiveXP project
http://livexp.boot-l...rtualBox.script


More:
I tried to add audio support, for now unsuccess. Will be checked later (some lines added which has no effect on script)

2nd iso:
(named as guest additions trouble)
I noticed,
issue is script or vbox making "ide secondary master" as the primary boot device + vbox adding previous .iso to "ide secondary master" if available. previous iso do not have to be VBoxGuestAdditions.iso

an easy reproducable way to repeat the issue:
build a project in one folder and use vbox script, than build same project on another folder and use vbox. Here the first build's iso boots.
(for now, be carelful when testing your project with this script)

I feel if iso added to "ide primary master" this would fix ?!?!?

anyway, I leave the rest.

ps:@amalux, yes I use same way too

[pecd.net]

if i understand you right, you are talking about the issues with missung quotes around the projectname (as i said here http://www.boot-land...?...&p=92037)...

or did you fix anything else?

@Peter: Please fix the missing quotes as i mentiones here http://www.boot-land...?...ost&p=92037

[Lancelot]

Hi ctmag

Where I was mistaken: I trusted psc preparing nativeex scripts fully compatible to any folder (and name related things), as a result I never thought there would be a bug related to this.

missung quotes around the projectname

yes, as you mentioned before, this is one of the fix I made with the blue text

or did you fix anything else?

2 projectname do not like dot (.) , also fixed with a workaround (I did not check all special charecters and I feel not necessary)
3 basefolder name issue fixed (red text) (which was the main reason this script not worked for me since I report it is not working)

compare the virtualbox script at nativeex I took http://lancelot.winb...201002241046.7z
with the one at LiveXP http://livexp.boot-l...rtualBox.script


for me 1 issue left
boot order of iso files issue ( "ide xxx master (CD/DVD)" )
vbox automagically adds "extra" entries from guid by adding them to the top of "boot order"

I feel if iso added to "ide primary master" this would fix ?!?!?

another idea as a workaround: script adding additional dummy (empty .iso files) entries to empty ide slots

[Lancelot]

one problem i have:

it does not work when the project name has a space in the name...

some quotes need to added...

Hi Ctmag

It does not work even when we have guotes . I removed quotes (#$q%BoxName%#$q --> %BoxName% back to original) since I already use workaround to fix.
-dot(.) replacement removed (not required, my mistake)
+audio support added (thanks kare)
+multi iso issue fixed

Now working without any issue with vbox 3.14, I hope you like.

http://livexp.boot-l...rtualBox.script

[pscEx]

I removed quotes (#$q%BoxName%#$q --> %BoxName% back to original) since I already use workaround to fix.

Your remove of spaces and dots coming from the %ProjectTitle% is ingenious! I'll add to nativeEx's script.

Peter

[Lancelot]

Your remove of spaces and dots coming from the %ProjectTitle% is ingenious!

Wrong, I only remove dots spaces.
Besides, my goal was having a working fixed script (which was not working), not a perfect one. Now it works

I'll add to nativeEx's script.

I only made minor additions to make it usable for everybody. I will be glad if you make required changes to make the script perfect.


edit:

[pscEx]

StrFormat,REPLACE,%BoxName%,.,_,%BoxName%

StrFormat,REPLACE,%BoxName%,#$s,_,%BoxName%

???

Peter

EDIT: Two things to discuss:

#1: I want to add "If,nativeEX, use %BurnISO%"; "Else use %ISOFile%".
What do you think?
In nativeEx %BurnISO% is used for many things, even for caching (as far as I remember).
I introduced it, because %ISOFile% as constant was not sufficient in some conditions. Here %BurnISO% is different from %ISOFile%

#2: If you can use my modified script, we should syncronize the versions.

[Lancelot]

???

Peter

old news (old script). I wrote post #39 script updated and wrote small info about update.

#1: I want to add "If,nativeEX, use %BurnISO%"; "Else use %ISOFile%".
What do you think?

I try to avoid things that can be missed with %BurnISO% on LiveXP, so I added 2 lines to the script

[Process]

Set,%ProjectsISOFile%,%ISOFile%

//Set,%ProjectsISOFile%,%BurnISO%

for nativeex change it to

[Process]

//Set,%ProjectsISOFile%,%ISOFile%

Set,%ProjectsISOFile%,%BurnISO%

that is all.

#2: If you can use my modified script, we should syncronize the versions.

You know I always want syncronisation on scripts. Check current script on LiveXP first.

[Lancelot]

#1: I want to add "If,nativeEX, use %BurnISO%"; "Else use %ISOFile%".

Thinking again,

something like following instead of current first 2 lines on [Process] (I say script for livexp server)

[Process]

StrFormat,LEFT,%ProjectTitle%,8,%ProjectTitleTest%

If,%ProjectTitleTest%,Equal,nativeEx,Set,%ProjectsISOFile%,%BurnISO%

Else,Set,%ProjectsISOFile%,%ISOFile%

what you think ?

[pecd.net]

Hi Ctmag

It does not work even when we have guotes . I removed quotes (#$q%BoxName%#$q --> %BoxName% back to original) since I already use workaround to fix.
-dot(.) replacement removed (not required, my mistake)
+audio support added (thanks kare)
+multi iso issue fixed

Now working without any issue with vbox 3.14, I hope you like.

http://livexp.boot-l...rtualBox.script

Thanks Lancelot....i am a bit busy...i was hoping to do it myself earlier...good work!!

[pscEx]

Thinking again,

something like following instead of current first 2 lines on [Process] (I say script for livexp server)

[Process]

StrFormat,LEFT,%ProjectTitle%,8,%ProjectTitleTest%

If,%ProjectTitleTest%,Equal,nativeEx,Set,%ProjectsISOFile%,%BurnISO%

Else,Set,%ProjectsISOFile%,%ISOFile%

what you think ?

Similar I wanted to do, with the difference that instead %ProjectsISOFile% %BurnISo% remains. The local change of the (in nativeEx) permanent value does not hurt.

Peter

[Lancelot]

Hi psc,

I avoid another permanent value since it is redundant to me. (I avoid using permanent for every solution, for this case we do not need to have a new permanent variable)
Besides, it seems much more easier to me for further use. (prevents many things that might happen)

I just updated the script, please test in nativeex world
http://livexp.boot-l...rtualBox.script

if it works as you expect (which should), no need to change the auto iso selection routine and can be directly syncronised by you setting script version=35 and deleting Description=(v34f) as usual.

[pscEx]

Looks well and I think it is usable


I have to test in all nativeEx combinations. And that takes a bit ...
Currently I'm in the middle of debugging "Reg2WBS full unicode support for WB 080".

And I want to finish that first.

Maybe tomorrow night i'm ready for test.

Peter

[Lancelot]

Looks well and I think it is usable

Currently I'm in the middle of debugging "Reg2WBS full unicode support for WB 080".

And I want to finish that first.

yummy, can you give some tips,
as far as I understand, none ansi will be detected and converted to binary with RegWriteBinEx ? or ?

[pscEx]

as far as I understand, none ansi will be detected and converted to binary with RegWriteBinEx ? or ?

Yes, Sir!

Current Reg2WBS converts Unicode of regedit version 5 "quick and dirty" to ansi:
Just skip the second byte.

If (what is usual) that is 00, no problem. And when it is not 00 ...

The new version works internally fully with WideStrings and outputs what is necessary: Maybe ansi string, maybe binary using WB80's RegWriteBin.

Peter

BTW: HoJoPE is the next candidate for this "Upgrade"