OK, now that I have LiveXP with all the tools I need and booting reliably from CD, I'm looking at putting it on a USB stick. So I'm trying the WIMPack and BootSDI scripts.

Boot SDI dies with a "You need SETUPLDR.BIN of W2003 SP1!" warning and then two " Run - Failed to find section [Calculate] in file: [%BaseDir%\Temp\livexp\calc.txt]" errors. I presume the first warning created the two errors.

I have "I provide the files" checked in BootSDI.script, and "%GlobalTemplates%\BootSDI" in the "at" edit box. In E:\WinBuilder\Templates\BootSDI\ I put setupldr.bin extracted from WindowsServer2003-KB889101-SP1-x86-ENU.exe, 24 March 2005 8:33:44 PM, 298,096 bytes. Worked with BartPE pe2usb, did not work with BootSDI.

I tried the version that comes with FlashBoot, 260,288 bytes and a date that's obviously not the creatino date, and that also did not work.

I'm sure I'll have more questions but first: where can I get the correct setupldr.bin?

Dont worry, you got the right files.
What you need to do is:

build livexp with boot-sdi. Copy BootSDI.img and WIMs\WIMs.vmdk to usb ,

Read: 9b. Boot from a properly formatted USB stick/disk
http://www.911cd.net/forums//index.php?showtopic=19333

I can't build LiveXP with BootSDI. See the second paragraph of the first message.

Read here:
http://www.911cd.net/forums//index.php?sho...19676&st=27

jaclaz

JonF

than lets go step by step and start a fresh trial:

1) Download livexp with "recommended" option
2) add ramdisk.sys and setupldr.bin to %GlobalTemplates%\BootSDI\
3) add wimgapi, wimfltr.sys, WindowsXP-KB914882-x86-ENU.exe, imagex.exe, srvany.exe to %GlobalTemplates%\WimPack
4) enable wimpack script
5) enable bootsdi script
6) follow picture: http://i487.photobucket.com/albums/rr238/l..._latest-exe.png (currently 075b5A)


I tested this now, and it builds and works nicely with vmware. What is your result??

If this test fails with your trial, please attach log file and what is your hostos?



ps: link jaclaz gave is about booting .iso file with ramdisk.sys method, to boot LiveXP.iso with that method,
1) enable createiso script
2) on createiso script enable "i provide setupldr.bin and ramdisk.sys"
3) make your build (**** i advice your iso be about ~475mb )

Edit: qemu changed to vmware.

Actually link jaclaz gave is about a way to get the "right" files.... nothing more, nothing less.

AFAIK BootSDI uses ramdisk.sys as well - WIMPack is optional/unrelated to BootSDI.

http://209.85.135.132/search?q=cache:QvLJz...sdi+ramdisk.sys

Or has it chaged?

jaclaz

You are right jaclaz, WIMPack is optional for BootSDI. In first post JonF wrote "So I'm trying the WIMPack and BootSDI scripts." so i gave steps including wimpack

And thank you for cache link, you are the master

Edit to may previous post: test with another virtualization software than qemu (i tested with vmware and it works nicely)

Well, on that page at http://www.911cd.net/forums//index.php?s=&...st&p=132420 I see a link to a Rapidshare download which contains two different copies of setupldr.bin. Neither of them work, yielding the same error message. I don't see any other links in that page to any source of the files.

I've disabled all apps and drivers, and if I turn off BootSDI and WIMPack and turn on CreateISO, I get a bootable ISO: so it's definitely a problem in BootSDI. It looks as if it's looking for a particular string of bytes at the beginning of the file. Since it's rejecting the setupldr.bin extracted from Server 2003 SP1, I wonder what would happen if I edited out that test.

JonF
i dont think it is a file problem, but here is md5checksums of the filess i use
md5: 0F1CE9CBCD35A30D285C1EB672092778 *RAMDISK.SYS
md5: 4352373BC08FFA6D8FFDB20A3BA5BC9A *SETUPLDR.BIN

also i dont think it is a bootsdi script or wimpack script problem too as i already tested them (2 times with and without wimpack option) with recommended livexp.

Livexp server seem to be offline now, please make test at post #5 when livexp is back online.

Arrrgggghhhh!

%GlobalTemplates%\BootSDI doesn't point to E:\WinBuilder\Templates\BootSDI, it points to E:\WinBuilder\Workbench\Common\BootSDI. Now there's a counterintuitive value!!

There's a no-good setupldr.bin there. I have no idea where it came from.

I sure wish there was some documentation for these global variables. Oh well.

Now it chokes on the line "TXTAddLine,"%TmpScript%","[dummy]","Place",2", which looks straightforward but fails:



Wonder if that's a probelm with beta 5 G?

Well, with my non-fresh copy of LiveXP and the WinBuilder beta 5 A encoded, it fails for me. Vista Ultimate 32 bit. Log file.

@JonF

Do not look at MD5. They are different on different language files.

But after you spent so many time in successless trials, maybe you 'waste' some more time:

• Download nativeEx_Barebone_075 and unzip into an empty directory
• Define source CD as usually
• Open Basic > !WBManager > WBManager and Restore Set 'Standard_BootSDI'
  This will build a constellation with an old version BootSDI w/o WIMPack
  (I thought that WimPack does not bring remarkable advantages for the PE, besides it seems to be 'more technical', and therefore I did not include)
  The constallation will also define VirtualBox as emulator. If you do not have it, please change to qemu
• Copy the needed files to %GlobalTemplates%\BootSDI, that means %BaseDir%\Workbench\Common\BootSDI
• Build the project

If it does not run into the emulator, there is really somthing wrong with the files you use.

As already reported some times, they MUST be from w2003 SP1, usually called W2003 R2

Peter

Coming soon in some latin days



i dont think so, but in case official wb version for livexp is wb075b5A and comes with the livexp package as shown in 6th step of post5


1) TRY only enableing BootSDI (disable wimpack) (dont forget 2nd step on post5)

2) Where is your wimpack on wb gui (Example: CreateISO is: Finish-->2 Create Image-->Create ISO)


Edit:
psc look post 1---------> "WindowsServer2003-KB889101-SP1-x86-ENU.exe"

When I started the 'nightly previews' I explained that there might be some inconsistencies.
I clearly said, that the preview is thought to shorten the time between a 'fixed' in the bug tracker an testing the result.

And I think that my post also made clear, that projects have to rely in the 'official' beta versions 4, 5, 6 (coming soon), ...

I'm sure that the preview always works with the combined nativeEx_barebone project(which also is changed to fit the new conditions, if necessary)
Here seems to be the problem that

• You use beta 5 G outside nativeEx_barebone_075
• A script is not assimilated to beta 5 G

Peter

@JonF

Thanks for the log, it gave me an idea
Can you try a build, and fail and than attach this file %BaseDir%\Temp\livexp\$$$.script

@JonF
Forget my posts!

It looks like Lancelot is on the way to solve the issue.
Peter

The last failures have been with beta 5 A ... as noted in my immediately previous message.

Here: http://vistape.fleming-group.com/$$$.7z. I compressed it in case line-end characters matter.

JonF

thank you,
It seems to me there wont be a very quick solution for vdk feature of wimdisk on vista,
for temporary solution, on wimpack script disable "Pack Wims Into VMDK container", i guess it will work for you.

At current, there may be a problem with your vista to mount .vdk images, we know vista have lots of protections that may cause this. Or maybe you used another utility with vdk before.....


Peter
it is not a drive letter problem, i tested with another Vista32 (protections already disabled, etc), drive letter worked, but next step failed with unsuccessfull copy, after format step, wim file copy failed, probably a format problem with vista, i will work on it.
An important question, what method should i use in scriptwriting to learn if hostos is vista?

wb must not delete ; started lines in .inf files , they are the 'gui' of pebuilder plugins . After writing all inf's i planed to use with wb, i discover wb deleted all my ; started lines , so i need to write them again in following days

couldn't post till now...

seems to me, someone wrote a tutorial on this around here somewhere LiveXP+BootSDI

If you still need a working bootsdi build, try this one; don't add or change anything, set your source as xp-sp2 and run it. If it works, I'll set you up with whatever programs you want.

And again for the record, the link I gave is this one:
http://www.911cd.net/forums//index.php?sho...19676&st=27

Where it is said that the TWO needed files, SETUPLDR.BIN AND RAMDISK.SY_/RAMDISK.SYS contained in Microsoft Diagnostics and Recovery Toolset (MsDart), formerly ERD Commander 2005 are the same as the Server2003 SP1 (which work).

To recap:
XP files do NOT work
Server 2003 files do NOT work
Server 2003 SP1 files work ALWAYS
Server 2003 SP2 files do NOT work (at least on a number of setups)
Server 2003 R2 files work

The link for the download of the release is this one:
http://www.microsoft.com/downloads/details...;displaylang=en

jaclaz

I remember troubles with mounting vdk images when they are ntfs compressed!

Peter

Hum. I was lazy, used XP SP3 as the source, and it worked ... with the minor error that no non-Microsoft programs on the destop or start menu have icons. Interesting ...

This worked not because you used "XP SP3 as the source", because your windows overcome the reason not mounting .vmdk image (maybe reason is hostos restarts, maybe other things). Now you get the screen i get with vista32 and in my trials i use "XP SP2 as the source".

So now 1st stage of problem passed , there is 1 more

2) psc, wimpack dont use ntfs compressed .vmdk images but you are close ,
After i looked hours,
I join psc club of blaming "Billy the Door"

Using this:

results with this


and than copying some .wim files fails as expected.

I guess jacklaz already may know things about this
What is the right command to use with vista to get empty ntfs formated image?



@psc
wb hanged after i gave permission to windows firewall of vista32 when winbuilder.exe downloading HPUSBF.exe. Screen stopped with "Downloading HPUSBF.exe" and continue stopping after i gave permission. Clicking STOP button didnt work and at last i close winbuilder.exe and restarted again.

@All
what should i use in scriptwriting to learn if hostos is vista?

Give me some time to do my personal experiments with this OS (which would not exist, if Billy the Door would think on technics (and accept intelligent users), not on $$)
I have my new 2 core 64 bit PC now , and fxscrpt gave me a (original, legal) Vista license

But I think the issue here has a rather simple explanation: The known HPUSBF.exe download links do not work since a while. Maybe the exe cannot be downloaded any more, maybe, the script has to be changed to an actual URL

The hanginig seems to be WB internal because of the broken URL, and I'll have a look on that and propably fix it.

Peter

What you posted tells me nothing.

How big was the image to be mounted and formatted?

How is it seen by VDK?

Something that proved to be the source of some problems was the "stupid" indexing service on XP, possibly the one in Vista is more aggressive/worse behaving.

As well shadow volumes or something dependant from it may affect strangely these kind of drivers.

jaclaz

No.

Right now I have two near-identical installations of WInBuilder, one downloaded from Amelux and one built up over time by me.

In Amalux's is WinBuilder.exe beta 5 l, in mine is WinBuilder.exe beta 5 A.

In Amalux's some of the scripts may be older versions.

I think all the tools are identical between the two installations, but I should probably triple-check that.

But in the two installations are exactly the same scripts (but maybe different versions), with exactly the same scripts selected or unselected, with absolutely every single option of every selected script set identicallly. (WIMPack is not selected). No app scripts are selected.

Amalux's works. Mine does not.

Gratulations for Amalux!
He is better!

Seriously: Here truelly is some difference hidden.

Can you make a log of both and compare?

If you do not have the tools to compare, you should not search and install.

Just post the two logs here. I and a lot of other members have the tools.

Or should be good to post at all. Some members see more than only one.

Peter

Try this one for your sp3 source

JonF:
No comment, For vista, I do all my tests with recommended download of livexp and source is xppsp2. I will try to upload it as a package for you to try.

As i wrote before, At least, with amalux's package, enableing wimpack + disableing "Pack Wims Into VMDK container" should be working for you now.

psc:

To make it clear, there are 2 problems
1) vmdk not mounted (driveletter)
2) cannot copy .wim images (vista32 format ntfs difference)

For 1)
I do NOT have 1st problem, but JonF says he gets this problem with livexp he downloaded, but dont get this problem with amalux ready package. livexp server is offline so i cant be sure.

For 2)
This is what i try to figure out and reported in my last post. JonF have this problem with amalux package too, follow my answer for jaclaz

besides i need 2 script writing help, one of them:
what should i use in scriptwriting to learn if hostos is vista???

ps: Welcome to x64 world



jaclaz:

Here is the info you would like

fsutil.exe file createnew test.img 34603008
vdk.exe open * test.img /rw /p:0
format F: /Q /FS:NTFS /V:Test /X /force

Result with vista32bit is:
Used Space: 10.006.528 bytes
Free space: 24.592.384 bytes
Capacity: 34.598.912 bytes

Result with 2k3x64 is:
Used Space: 2.556.416 bytes
Free space: 32.046.080 bytes
Capacity: 34.602.496 bytes

I guess you understand the problem Houston.

There are two ISSUES!
To the ISSUES: only the first one is important. If vmdk not mounted, 'second one' cannot copy.
But 'Why Not Mounted'? I think that you at least look at my 'ntfs compressed' post, and remove the compression, if there is any.

Jonf: Let me repeat my post that you publish BOTH logs here.

Thanks for the welcome.
But I have to disappoint you a bit:
As known, I'm a 'Certified Vista Enemy'
And therefore I did everything only to help 'those stupid uninformed people meaning to get some advantage by using Vista'

(Today I installed Vista. But please understand that I do not want to spend more than half an hour to explain all my (first) worries here)
Only one sample: Whenever I start WB, I'm asked whether I trust this unknown application.
IMHO when I once trusted, why ask next time ???

Please, no suggestions how to change. I only want to say, that a well designed OS has to remember my opinion.

Peter

JonF
1)
Here is another success i got, For temporary solutions, on wimpack script, enable "Pack WIMS into VMDK container" and choose 10 at freespace box. (you can increase-decrease number with your trials)

2)
Please download and test this. This is the Latest LiveXP which i used in all my tests in this topic.
http://lancelot.winbuilder.net/5F_WB_LiveX...0081213_Rec.rar
Lets see if you can get same results with amalux package?????



psc:
I think that you at least look at my post 24, answer already given to you there

I am close to you, I am a 'Certified Vista Disliker', i had same experience and opinions with you when i first installed for a trial. I test with vista32 only to help JonF. And underline difference between "Disliker" and "Enemy" i never use word stupid .

YES i am disappointed to see you dont still read carelfully , I never like vista, never used on my home pc (except test purpose like you), As written many times many posts, I use 2k3x64 and advice xp64 to any Windows users that wants to use Windows 64bit.


Completely disagree with you, for me 2nd one is uppermost importand and reasons written in my previous posts.

Also still asking:
what should i use in scriptwriting to learn if hostos is vista???

edited.

Sounds like a good idea. Logs.

Christmas party this evening. I'm going to try Amalux's version of this morning with WIMPack just to see what happens, then pack it in for the night ... no, I get two "List index out of bounds" in BootSDI.

"List index out of bounds" , common to me , for solution use wb075b5B i sent before (or a later version)

ps: wb075b5A used with all tests i made with vista32

At least one script is different: API (or the link to it in script.project)!
Try Amalux's API.script in your project!

Peter

No opinion yet!
I'm also an expert-dummie due to Vista.
Theoretically (if API etc. is working well) : NOTHING
(My statement excludes all Wow64 issues)

Peter

This error message is well known since a long time and usually the result of a syntax error in a script line.
In the past I inserted a lot of checks to avoid such errors. Just as result of a wrong entry in an input file, they should never appear in an app.
Most of the conditions are already fixed. But appearently there are still constellations not yet caught by the changes I made.

In this case I really need the COMPLETE project. Posting or PM here would go outside your bytes limit. So please mail to me.

Peter

Have fun in Christmas party.
Here no party

Here is a new wimpack script,
http://lancelot.winbuilder.net/5F/zz_v51_U..._%21WimPack.rar
New features:
**to avoid drive letter problem, there is "Stop and Remove VDK" button on gui. Drive letter problem happens after a trial of failure. So if you fail with a trial, before another trial click "Stop and Remove VDK" button on gui of wimpack (ps: i didnt add this to beginin of process as there are things to ask Galapo first and Galapo is not here)
**creating vmdk with fat32 (or fat) feature added and selected as default. This will prevent having copy error problem (not shown as error or warning on log) causing one of the .wim's not mounted when vista used.
**a check added to vmdk step so if vmdk mount fails for a reason, than build will stop.

JonF, for last time what i want you do is:
1) Extract winbuilder_LiveXP_20081213_Rec.rar to C:\
2) Extract zz_v51_UPLOAD_!WimPack.rar to C:\winbuilder_LiveXP_20081213_Rec\Projects\LiveXP\Basic\Shells\Addons
3) Copy HPUSBF.exe you have to C:\winbuilder_LiveXP_20081213_Rec\Projects\Tools
4) Open winbuilder
5) Enable wimpack
6) Click "Stop and Remove VDK" button on gui of wimpack script
7) Enable BootSDI
8) Make the build

I guess Case closed


I hope you like, happy Christmas


Edit:
Case closed= I mean Case mostly closed, to make ntfs feature more automatic with hostosvista (than manually selecting 10 as free space when ntfs+vista used) there will be more progress.

Merhaba Lancelot,


I'm using these lines to check hostOS Vista and its language:

[OSVista]
If,ExistFile,"%VistaInfo%",IniRead,"%VistaInfo%","VistaInfo","SourceType","%SourceType%"
If,%SourceType%,Equal,"VistaCD",Set,%OS%,"Vista"
If,%SourceType%,Equal,"WAIK",Set,%OS%,"Vista"
If,%OS%,Equal,"Vista",ReadENV,%DistLang%

Is it what you are looking for?


I've finished 3 days ago a PDF file that should explain the vars used and compare vars and path between liveXP and VistaPE, as I (wb rookie) am really getting worried about the used vars and tried to get sth like an overview. Will upload the file as soon as boot-land is online.
So maybe you can spare your time.
When the file has been uploaded you're invited to correct and improve it.

Regards,
Walter

Meow Walter,

Thank you for all support,

Sadly No, You are checking sourceos, this is not what i am looking for, i want to check hostos (the os mostly user uses to play computer games, to listen music, to try winbuilder.exe etc).

Will be there

@Lancelot!

Back to the 'mount' issue.

Maybe you have a look int nativeEx_barebone_075, the script 'Test VMDK in VirtualBox'.

Here the status 'Mounted' / 'Unmounted' is stored in a variable.
And when beginning the script an eventually (by failure abort) mounted vmdk is dismounted.

Peter

Not fully what I had asked:

translates to:
run VDK VIEW on the mounted image or VDK IMAGE on the unmounted image.

Where do the "strange" 34,603,008 come from?

The size appears to be compatible with VDK default geometry of mx64x32. 33x64x32=67584 sectors x 512 = 34,603,008
But the default on NT based systems AFTER NT 4.00 is nx255x63.
Would it be possible that Vista (one of the two editions or both) interpret wrongly this non-default geometry?
Why don't you try with a nx255x63 AND a .pln file?
4x255x63=64260 sectors x 512= 32,901,120
5x255x63=80325 sectors x 512= 41,126,400
http://www.forensicfocus.com/index.php?nam...sc&start=42

jaclaz

@Lanzelot!

Please have a look tonight into nativEx_barebone_075 with WinBuildwer beta 5 H

There vill be a variable %HostOS% with possible values NT, W2000, XP, W2003, Vista.

To decide hostos beeing 32 or 64 bit, is still possible with %Wow64% (as long as WinBuilder.exe is 32 bit)

BTW: In nativeEx based projects currently projectinfo.ini contains a line like
[Created]HostOS=Microsoft Windows XP [Version 5.1.2600]
6000 or 6001 => Vista

Peter

jaclaz

I get it from log file of my tests with winbuilder-wimpack

Here are test results i get with 3 values using this batch:



i change xxxxxxxx to
32901120
41126400
268435456

and take properties picture at pause step

http://lancelot.winbuilder.net/5F/vdk_vist...ts_20081214.rar



Also i made this tests (i maybe mistaken, if so very very sorry):



Results were same above because at "vdk.exe open * test.img /rw /p:0" step, vdk.exe dont take test.pln file to consideration as seen in picture (or maybe i made something wrong), here is xxxxxxxx=32901120 result:
http://img257.imageshack.us/img257/7248/32...dmakeplnfy3.png


Pezer,

Thank you but it may not be solving the problems JonF reported (and i confirm) because problem happens when there is an existing mounted image causing drive letter getting wrong, instead i made a simple write test for writeable drive and vdkremove button for incase situations (except vista, this never needed before). I guess it is better to close all vdk before creating new one, as problem is solved mostly with using fat/fat32 vmdk and as we have some tips to use with ntfs, better to leave further decisions to Galapo. I greatly hope JonF will have success with my last instruction with new wimpack script.


%HostOS% is a great idea Thank you
and thank you for projectinfo.ini info

Er, maybe not. I did exactly this:

1) Extract winbuilder_LiveXP_20081213_Rec.rar to C:\
2) Copy Workbench\Common \BootSDI and Workbench\Common\WimPack folders
3) Copy HPUSBF.exe you have to C:\winbuilder_LiveXP_20081213_Rec\Projects\Tools
4) Open winbuilder
5) Enable wimpack
6) Enable BootSDI
7) Make the build -- same results as before - failed
8) Extract zz_v51_UPLOAD_!WimPack.rar to C:\winbuilder_LiveXP_20081213_Rec\Projects\LiveXP\Basic\Shells\Addons
9) Click "Stop and Remove VDK" button on gui of wimpack script
10) Make the build same -- results as before - failed

winbuilder_LiveXP_20081213_Rec-logs.7z

JonF

you missed updating wimpack script in your trials (as described in my 2) step) and you cant do 9) step you described without updating wimpack script ,

with the steps you follow, i dont surprise you get these logs:
log_run1.html --> ntfs issue, (2) issue described before)
log_run2.html --> drive letter issue, (1) issue described before)

here is revised steps for you:

0) Delete C:\winbuilder_LiveXP_20081213_Rec\ folder
1) Extract winbuilder_LiveXP_20081213_Rec.rar to C:\
2) Extract zz_v51_UPLOAD_!WimPack.rar to C:\winbuilder_LiveXP_20081213_Rec\Projects\LiveXP\Basic\Shells\Addons
2b) Copy Workbench\Common\BootSDI and Workbench\Common\WimPack folders you have
3) Copy HPUSBF.exe you have to C:\winbuilder_LiveXP_20081213_Rec\Projects\Tools
4) Open winbuilder
5) Enable wimpack
6) Click "Stop and Remove VDK" button on gui of wimpack script
7) Enable BootSDI
8) Make the build


edit: at log_run2.html is ntfs issue ---> drive letter issue

JonF: If you cant 0) Delete C:\winbuilder_LiveXP_20081213_Rec\ folder , than follow steps: 2), 4), 6), close winbuilder, than try to delete.

Er, no, I didn't miss updating wimpack.script. See my step 8. (I left out step 8a, clicking Refresh in WinBuilder). Iwrote that I clicked "Stop and Remove VDK" button on gui of wimpack script because there was a "Stop and Remove VDK" button and I clicked it.

JonF

your logs say you use wimpack script v50 , but i sent v51

and as you see "Stop and Remove VDK" now, than lets repeat the test.

1) click "Stop and Remove VDK" on gui of wimpack script
2) click "Clean Temporary Files" on gui of LiveXP main script
3) make the build

Sure , if you open test.img how do you expext VDK to "take into account" info in test.pln?

Try again with "vdk.exe open * test.pln /rw /p:0"

jaclaz

P.S.: On second thought - and unrelated to this problem- why is VDK.EXE used at all?
I mean, if you create an empty file with fsutil, and mount and format it, it will be a superfloppy device (no MBR).
As such it can be mounted and formatted by IMDISK or FILEDISK.
Or is there the need to access it with \\.\PhysicalDrive syntax?

Check this:
http://www.911cd.net/forums//index.php?showtopic=19333