21 replies to this topic

[patsch]

Today I updated the 4-iso.script
With that new script v.25 it is no longer possible to get a multiboot project. Grub4Dos is selected in main configuration but is not integrated in the final iso, win7pe starts directly. Going back to the old version v.22 and everything is fine again

[sbaeder]

And we can only really help out here if we see a LOG FILE - or maybe a good idea wold be to generate TWO log files (without the time info) and compare them to identify the differences, etc...

Scott

[patsch]

here are 2 log files ... the one from yesterday with the old script version v.22, the one from today with the new version v.25

http://www.fileden.c...Nov-13_18-41.7z
http://www.fileden.c...Nov-14_15-24.7z

History of the script

History023=Lancelot new IniVariables added
History024=Lancelot CheckBootMGR removed (already exists at mainconfig)
History025=Lancelot AutoBootMGR replaced // PressAnykey enhanced

[sbaeder]

Something wrong with links??? (only part of the line is the link???)

But I had v22, and can go get v25, so will look at them too...

[patsch]

sorry, i had to use the bbcode, otherwise the forum software displays the links not correctly

[sbaeder]

You could also just make it be text I have to cut/paste

Also, did you update JUST this script - OR all the scripts...I noticed a lot of things (scripts) were updated... HOPEFULLY, they aren't updating the server until all the parts are working together...

I am noticing a lot of changes to the way they try to detect if it is supposed to be GRUB4DOS or "standard"...

[sbaeder]

I see a BUG in the script!!!

//--

// Based on selected boot manager, go run the proper stuff...

//--

//BootManager=Normal -> bootsect.bin -- if not exists --> etfsboot.com

If,%BootSector%,Equal,bootsect.bin,Begin

If,ExistFile,%targetdir%bootsect.bin,Begin

FileRename,%targetdir%bootsect.bin,%targetdir%bootsect.tmp

FileRename,%targetdir%bootsect.tmp,%targetdir%bootsect.bin

Set,%BootSect%,bootsect.bin

End

End

Else,Set,%BootSector%,etfsboot.com

In this, Lancelot tried to move this processing from a section of the script to in-line code, BUT - ot sure at all it is right...In any case, it totally screws up the bootsector variable...

I think it should be...

//--

// Based on selected boot manager, go run the proper stuff...

//--

//BootManager=Normal -> bootsect.bin -- if not exists --> etfsboot.com

If,%BuildModel%,Equal,Normal,Begin

  If,ExistFile,%targetdir%bootsect.bin,Begin

    FileRename,%targetdir%bootsect.bin,%targetdir%bootsect.tmp

    FileRename,%targetdir%bootsect.tmp,%targetdir%bootsect.bin

    Set,%BootSect%,bootsect.bin

  End

  Else,Set,%BootSector%,etfsboot.com

End

//

This is at about line 130...

[patsch]

thx, that was the fault, everything works fine again

[sbaeder]

OK - also left a PM for Chris to fix server (v26??)

[Wonko the Sane]

@sbaeder

OT , just for my personal knowledge, can you explain to me what these two lines actually do?

FileRename,%targetdir%bootsect.bin,%targetdir%bootsect.tmp

FileRename,%targetdir%bootsect.tmp,%targetdir%bootsect.bin

Wonko

[MedEvil]

If i remember correctly, that is used to make sure the filename has certain letter casing.

[pscEx]

If i remember correctly, that is used to make sure the filename has certain letter casing.

Peter

[patsch]

v.26 of the script is now on the server and it works

[Wonko the Sane]

If i remember correctly, that is used to make sure the filename has certain letter casing.

So the FileRename function accepts as input "case INsensitive" BUT outputs "CaSe SeNsiTivE"?
Thanks.

Maybe this piece of info could be specified here:
http://code.google.c...wiki/filerename


Wonko

[MedEvil]

So the FileRename function accepts as input "case INsensitive" BUT outputs "CaSe SeNsiTivE"?
Thanks.

Maybe this piece of info could be specified here:

What? We should specify, how windows works?

What are you doing reading scripts anyway, if you don't even know basic windows functionality?

[sbaeder]

He knows, but it's not that "intuitive" from just looking at the lines involved, and they were in the pasted in code above (so he didn't go poking at the script)...

Windows will create a file with whatever case you use - i.e. creation is "case SenSiTiVe", but lookups are always Insensitive as MedEvil stated...yes, that *IS* the way windows works...But tools like Grub4dos, even with it's dos-ness added to basic "grub" is still insiting on lookups that are sensitive to the CaSe used!

Oh well...


Scott

[Wonko the Sane]

But tools like Grub4dos, even with it's dos-ness added to basic "grub" is still insiting on lookups that are sensitive to the CaSe used!

It's not really grub4dos, which is CaSe SeNsItiVe ONLY on CDFS.

BTW, ad example Windows 2K/XP/2003 (cannot say later) Install disks are also CaSe Sensitive.

When making a BartPE, which some of you may be familiar with, in some cases the little paraglider's tool toupper.exe is used:
http://www.paraglide...ies/toupper.htm

And to cite a known program, Winimage in some cases makes strange things inside images, Capitalizing First Letter of a filename..


Wonko

[MedEvil]

BTW, ad example Windows 2K/XP/2003 (cannot say later) Install disks are also CaSe Sensitive.

Just the files named in setupldr are case sensitive. Because the names arn't treated as a row of letters, but as a row of charcters.
Just hexedit setupldr to reflect your favorite casing.

[Wonko the Sane]

Just the files named in setupldr are case sensitive. Because the names arn't treated as a row of letters, but as a row of charcters.
Just hexedit setupldr to reflect your favorite casing.

Yes/No.
http://www.911cd.net...showtopic=11192
http://www.911cd.net...showtopic=16400


Wonko

[MedEvil]

What the heck with the links again?

Both lead to threads, where people solved their problems uppercasing everything. That's like leveling a single building with an atom bomb!

If that's the way you roll, great do it! Just don't tell the rest of the world, that that's the only way to do it.

I have for years a nice PE with my favorite casing. First letter uppercase, rest lower case, extension all lower case.

Took some hexediting, but it boots fine.

[Wonko the Sane]

If that's the way you roll, great do it! Just don't tell the rest of the world, that that's the only way to do it.

Never pretended that this is the "only" solution or the "right" solution, sorry if I gave you this impression.

Anyway, the given links are not about uppercasing "everything", but just a bunch of files, which I presume are the same or mostly the same you change by hex-editing.

Only pointing out how things are "strange" when using CDFS and some files (both grub4dos and MS) or some tools (like mkisofs in the various builds)...

BTW, if I remember right original MS discs also used, besides all upper case 8.3 file format...

I have for years a nice PE with my favorite casing. First letter uppercase, rest lower case, extension all lower case.

Good for you.

Maybe if you would detail your solution, that will be an alternative that a lot of peeps still playing with PE 1.x builds will gladly adopt.


Wonko

[MedEvil]

Like i said, i hexedited the filenames in setupldr to my liking and of course in the bootsector.