Firadisk? win2k3_RAMdisk? errors? Frustation.

I have two problems.
one is when i try to use Firadisk as my ramdrive, and NOT Win2k3_Ramdisk - i get this error when building

Generated by psc program 'WBVerify' version 2.2.3
Date: 2010-Oct-22 19:50:18

[Counts]
Missing=1
Obsolete=0
Errors=1
Warnings=0

Because of missing files some results may be wrong

Missing: Title: autoUPX

Errors:
"Using BootSDI with bootsect.bin as bootsector requires enabling Win2k3_Ramdisk script"

if i enable win2k3_ramdisk + Firadisk, everything works-until i get to my bootsdi.script.
i get 3 warnings

log
http://www.mediafire...hdqd9iikklwc3i9

my livexp is going to be a very small build. so im not needing to be able to support anything over 250MB.
whats the best combination to go for ramdisk + Bootsdi? or do i even need to use bootsdi.

i just want a vast-PC-compatible/fast/reliable livexp build.

whats the best method?

hi i m not very familiar with winbuilder because i still use bart pe
but i have created a script to create an image of pe to boot from ramdisk from grub4dos with firadisk. i think this is what you want.

for my script to work i need a output folder of your winbuilder project and you must build your winbuilder project with firadisk script and disable any other script like the sdi script .
no need of iso creating script

you just need to build your project with the scripts you want + firadisk script.
then download my batch script which will create the image for you


this is the thread i have started on 911cd
http://www.911cd.net...o...=24100&st=0


download : http://www.mediafire...xha70sc1q05gl6u
added devcontrol by paraglider

files to be downloaded
contig.exe

Edited by Rajesh2010, 23 October 2010 - 03:59 AM.

thank you for giving me a different option.
i really do appreciate it.

i dont even care if i use firadisk or not.
i dont care what i use.

all i want is a vast-PC-Compatible/fast/reliable Livexp build..and i dont care what methods i use to get there.
and it seems im looking at Win2k3_ramdisk, Firadisk, Bootsdi, Wimboot, and wimpack to get me there.
and im not sure which ones i should use.

like i said, from what i have read - Firadisk is used for BIG livexp builds....my build is around 200MB.
Im an IT Tech, and am needing this Livexp build to work with many types of computers, old and new; as well as be fast to boot.

i thank you for your input Rajesh2010, but im trying to stick with the stock winbuilder way of doing this. i will definitly keep your advise in mind as an option though.

@dsolomon
the script i have written does not care whether your livexp is built from winbuilder or pebuilder
it just needs output folder of the winbuilder .thats it

it just need a livexp built with firadisk thats it
you dont have to read my thread to get around it
just download the batch script from links i gave and also the program contig.exe

and run the script

Also To Note:
I am getting the 3 warnings mentioned in my initial post from the bootsdi.script.
i have done a little testing - and if i choose the wimboot.script instead of bootsdi.script - i do not get the 3 warnings.

disable the bootsdi script and that win2k3 ramdrive script
disable iso create script

just build normal livexp with firadisk

thats it

i just need output folder

regards

all i want is a vast-PC-Compatible/fast/reliable Livexp build..and i dont care what methods i use to get there.
and it seems im looking at Win2k3_ramdisk, Firadisk, Bootsdi, Wimboot, and wimpack to get me there.
and im not sure which ones i should use.

FWIW, having tried all combinations, I use only Wimboot and supply the Win2k3 files as directed in that script's interface. This keeps the ISO tight, fast and fully portable, same image boots from CD/HDD/UFD/USB etc. and I've yet to find a machine I couldn't boot successfully with this image.

@dsolomon
i forgot to mention that
also disable wimboot.script

just make plane livexp+firadisk
without bootsdi ,wimboot,win2k3ramdisk,iso creating script

report if you have problem

still if you want to use the bootsdi ,wimboot,win2k3ramdisk script u have to ask the other members who are using winbuilder

regards

FWIW, having tried all combinations, I use only Wimboot and supply the Win2k3 files as directed in that script's interface. This keeps the ISO tight, fast and fully portable, same image boots from CD/HDD/UFD/USB etc. and I've yet to find a machine I couldn't boot successfully with this image.

if i used wimboot + wimpack would that be as stable?
would it be better if i just used wimboot without wimpack?

if i used wimboot + wimpack would that be as stable?
would it be better if i just used wimboot without wimpack?

Yeah, don't use wimpack, it serves no purpose with Wimboot and causes issues AFAIR.

ok i have decided to use win2k3_ramdisk + wimboot only for my project.
all works well.

but i have stumbled upon another problem.
when my iso is created, i am left with a "LiveXP_WIM.ISO" and a "HddBoot" Folder.
it appears i need both to successfully boot from a cd (rather than qemu)

what am i doing wrong? im assuming i need the "Hddboot" Folder in my "LiveXP_WIM.ISO"
do i need to slipstream the "Hddboot" Folder to the root of my "LiveXP_WIM.ISO" manually?
screenies below. will post Log tomorrow morning.

ok i have decided to use win2k3_ramdisk + wimboot only for my project.
all works well.

but i have stumbled upon another problem.
when my iso is created, i am left with a "LiveXP_WIM.ISO" and a "HddBoot" Folder.
it appears i need both to successfully boot from a cd (rather than qemu)

what am i doing wrong?...

Not nearly so complicated , the HddBoot folder is not required at all. It's supplied as an easy way to setup a USB HD (if wanted); from the tutorial:

Setting up an external USB HD

New Method - With the advent of WimBoot builds, this has become very simple; when a project completes, you will find a folder named ISO in your build directory; this is the folder containing your finished ISO (used to burn CD or boot from directly on hdd/ufd etc.) but it also contains a folder named HddBoot which contains all the files you need to boot an external, USB hard drive! Save your data, format the drive (NTFS) and copy the files to the new primary, active partition on your USB HD.

fyi, you don't need the win2k3_ramdisk script; just supply the win2k3 files in WimBoot script. The WimBoot script is self contained (unlike BootSDI).

@amalux

just supply the win2k3 files in WimBoot script. The WimBoot script is self contained (unlike BootSDI).

Hi amalux,

wimboot only requires setupldr.bin from 2k3sp1, it does not self contain traditional 2k3sp1 files

Traditional 2k3sp1 files are ramdisk files,
2k3sp1 ramdisk requires both setupldr.bin and ramdisk.sys from 2k3sp1,
and since ramdisk (2ksp1 ramdisk, firadisk, winvblock) have a wide usage with both CreateISO and BootSDI BootDI scripts, they are seperated.

If not seperated than we need to fill both create iso and BootSDI BootDI scripts for all 3 ramdisk options, guess rest....


@Rajesh2010

just a tip to avoid confusion, for your tool to work, create iso script must be enabled

@Rajesh2010

just a tip to avoid confusion, for your tool to work, create iso script must be enabled

thanks..
but could you explain the reason
i have downloaded winbuilder
but i have never used the winbuilder to build my pe because i have fully configured bartpe for my personal use
as far as i know every script does what it is made to do
my script does not need the ISO
it only need the output folder
and then it creates an HD image say pe.img which is loaded by grub4dos

regards

Edited by Rajesh2010, 24 October 2010 - 08:22 AM.

but could you explain the reason

Sure

create image scripts, before creating image, also make "pre image" tasks......

Very well known pre image task is, with default settings, shortcuts (userprofile folder) packed to a package (modelram.exe),
when pe1 boots,
this package extracted to ramdisk (B:\) (--> after extraction B:\Documents and Settings + subfolders + StartMenu containing .lnk files)


trying to explain "basically" in pebuilder way :
imagine you have zz_profile.inf (zz to have at end )
which converts shortcut information to .lnk files to form a startmenu and make ready folders,
since pebuilder only creates iso, no problem disabling create iso step there.

following story, we can say on livexp, "zz_profile embedded into '2 Create Image' scripts"


well this is only profile part of the story, there are also other zz tasks and other things, I try to keep as short as possible to get you the picture.

Shortly:
At least CreateISO must be enabled to use tools over PE like in BartPE

@Lancelot
ok i got the idea
but the name of the script is misleading
i would suggest to separate the process of preprocessing from creating iso
and create iso should only create iso

there should be 2 scripts
1.preprocessing (core script )
2.create iso

wimboot only requires setupldr.bin from 2k3sp1, it does not self contain traditional 2k3sp1 files

I only meant that it doesn't require a separate Ramdisk script, not that it doesn't require files

If not seperated than we need to fill both create iso and BootSDI BootDI scripts for all 3 ramdisk options, guess rest....

BootDI scripts, is this something new?

Hi amalux,

I thought you were requesting with critisize and felt to explain the situation....
Recent spam advertisements on livexp section probably made my thinking not fluent, sorry for misunderstanding.

BootDI scripts, is this something new?

Hehe Story is:
last year some time, I was tired seeing jaclaz posting same things again and again about name of project + BootSDI not being SDI, (probably 1000 times already).
I asked him we can change script name and project name but he said this will break all posts so far in forum, (well, for today, I am glad he rejected that times)
For midway, I changed description of both project and bootsdi, but this did not satisfy jaclaz and he continued writing same things again & again.
Since than, finding another midway, I decide to write BootSDI with the form "BootSDI BootDI"
probably this will also not satisfy too, but at least number of such posts decrease.

Well I can not solve everything with midways, I still do not know how to get rid of spam advertisements on livexp section, I guess better to delete them

Not nearly so complicated , the HddBoot folder is not required at all. It's supplied as an easy way to setup a USB HD (if wanted); from the tutorial:


fyi, you don't need the win2k3_ramdisk script; just supply the win2k3 files in WimBoot script. The WimBoot script is self contained (unlike BootSDI).

life is good my friend. i disabled all Ramdisk scripts and am using wimboot and supplying the win2k3 files.
all works! thank you for your guidance.
life is good!

Hi Rajesh,

I really understand you, I am an old pebuilder user too, still think it is great and advice pebuilder projects time to time when I feel this is what end user needs. (check teuton pe when you have time )

but on livexp, there are also other things.

as an example:
on livexp, after build finishes, you can add another application to the build. (without building from begining which you can guess very good for verrrry slow wb) This requires .lnk file(s) (or maybe other files added userprofile folder) be in the packed package ....

There are also other tasks, I am keeping story short, too long story, but be sure we can not do what you sugggest easly,
The only thing that seems to please you is adding another create image script that does not create anything but only make final folder ready to be used by other tools,
well commenting out mkisof.exe & cdimage.exe lines will do that with create iso script, or an optional checkbox on script's interface ! ,
but so far not demanded by any livexp user at all since everything works smoothly.
I think it will not hurt creating an iso and see everything works fine on emulator before using tools to do other tasks

Hi dsolomon,

I am glad wimboot fixes your problems .

but in case if same issue appears again here what your issue was with bootsdi bootdi

you were using correct setupldr.bin but wrong ramdisk.sys on w2k3 ramdisk script

as far as I read (do not have files currently) ramdisk.sys version of 2k3sp1 is 5.2.3790.1830,
but the one you use have version 6.0.6001.18000 , which I guess you took another place than 2k3sp1
2k3 ramdisk script forgot to check ramdisk.sys version (since this never happened before)
but
bootsdi bootdi script being wiser (thanks to oriensol) figured out you are using wrong ramdisk.sys and halted the build.

well, I am sure you like wimboot more, only informing.


@amalux

for quick precaution, a revised version of [process-winxp] section maybe helpful for your next package.

[process-winxp]

If,Not,ExistFile,%pFileBox1%\ramdisk.sys,Halt,"ramdisk.sys file missing"

Retrieve,fileversion,%pFileBox1%\ramdisk.sys,%ramdisksysversioncheckinfo%

If,Not,%ramdisksysversioncheckinfo%,equal,5.2.3790.1830,Halt,"You need Ramdisk.sys of W2003 SP1!"

If,Not,ExistFile,%pFileBox1%\setupldr.bin,Halt,"setupldr.bin file missing"

Run,%ScriptFile%,Copy-W2003-Files

you were using correct setupldr.bin but wrong ramdisk.sys on w2k3 ramdisk script

as far as I read (do not have files currently) ramdisk.sys version of 2k3sp1 is 5.2.3790.1830,
but the one you use have version 6.0.6001.18000 , which I guess you took another place than 2k3sp1
2k3 ramdisk script forgot to check ramdisk.sys version (since this never happened before)

That is some great detective work and a good tip on the new check, I'll add it in

VERY good detective work, lancelot! kudos! lol

i do have one other question.
when using wimboot.script - everything works 100%
my only complaint is that it is somewhat slow to boot on a fast machine. (about 3 minutes)
which is not bad - but i would like to see if there is a way to speed this up.

i have conducted some testing, and from what i can tell - wimboot.script creates a "BootSDI.WIM" file that contains the below files and folders


my I386 folder is 144MB
my Program Files folder is 97MB

when i initially boot my livexp build - i have learned that the "BootSDI.WIM" is loaded during this process


common sense, as well as some light testing, says that if the "BootSDI.WIM" is smaller in size - then the boot-up time will be faster.

here is the kicker, is there a way i can load my "Program Files" folder in a different way?
perhaps, not putting the "Program files" folder in the BootSDI.WIM - then loading my "Program Files" folder in an alternative way (after boot time) ?

Perhaps, is there a way to make my BootSDI.WIM smaller? i hope im not asking for the impossible and i hope i am being clear in what im trying to accomplish.

What do you guys think?

also, just to be a little more clear, below is a screenshot of my 3 livexp drives (they are boxed in red)

IMDISK (B:)- is, of course, my writable "documents and settings" drive
Boot (X:)- is where my BootSDI.WIM is loaded into
WimPE (L:) - is the actual CD-ROM for my livexp build.

Hi dsolomon,

Yes we definately understand you , there are 2 ways provided by LiveXP.

I can not easly test before writing with not being at homepc,
mostly here with an old pc,
but from your replies I can figure out if I am mistaken...

1 way:
\Basic\Build\--> enable ProgramFilesPE script
on ProgramFilesPE "Define %ProgramFiles% Location" setting to "Run From CD"

give a try

common sense, as well as some light testing, says that if the "BootSDI.WIM" is smaller in size - then the boot-up time will be faster.

here is the kicker, is there a way i can load my "Program Files" folder in a different way?
perhaps, not putting the "Program files" folder in the BootSDI.WIM - then loading my "Program Files" folder in an alternative way (after boot time) ?

Perhaps, is there a way to make my BootSDI.WIM smaller? i hope im not asking for the impossible and i hope i am being clear in what im trying to accomplish.

What do you guys think?

Your right! That's the perfect explanation for why portable programs are better!!

Why load all your programs onto your boot disk (most you rarely use) and have to wait for a huge image to load every time? Just include the programs you always need and load the rest when or if needed. I never need a LiveXP image larger than 100MB (loads very fast) and have access to 100's of programs whenever needed, don't even have to reboot the PE. Even loading all the programs at every boot still doesn't slow down loading the image.

Also, whenever possible, load the image (ISO) from hard drive. Very easy to setup and you won't believe how fast it boots, under 30 seconds to full working desktop. I setup all my computers, XP and W7 with LiveXP and W7PE images, ready to boot at startup menu. Let me know if you need any help with setup

--
The only problem you'll find with Lancelot's method is a noticeable delay in response time when launching programs. Some people don't mind this but it really annoys me . Either way, let us know if you need help.