Topic: Problem after converting V5 to V6 files
started by: schd
Posted by schd on Dec. 14 2011,10:39
Hi,i'm using EasyBoot v5 on our Dell servers without problems.
Today i've installed v6.5.2 on a testcomputer and copied v5 files to it.
As mentioned here < http://www.ezbsystems.com/cgi-bin/ikonboard.cgi?act=ST;f=1;t=3514 > i saved all .ezb files once and created a new iso.
But after booting from this iso, i get a "Device=<82>" message on a black screen and a ~30sec delay before easyboot is starting.
Also tested on a vmware esx 4.0 virtual machine, message appears too, but no delay.
Any ideas how to solve this?
Regards
Posted by balder on Dec. 14 2011,11:04
@schdWelcome back @schd
Quote: "But after booting from this iso, i get a "Device=<82>" message on a black screen and a ~30sec delay before easyboot is starting."
Is it W2k3-BartPE (BartPE built from Win-2003-server) you are dealing with - you wrote a post mentioned this < HERE >
Or what kind of ISO-file (or build) is it you have problem with
Is it a different WinPE of some kind or is it some type of Linux-system
regards balder
Posted by schd on Dec. 15 2011,03:56
Hi balder,the iso is created from easyboot itself (main menu -> make iso).
Iso from V5 (fully working) - starting process:
Message Start booting from CD...
Easyboot logo appears (no delay)
Easyboot main menu appears
Iso from V6 (only saved .ezb files, nothing changed) - starting process:
Message Start booting from CD...
Message Device=<82>
~30 Sec delay
Easyboot logo appears
Easyboot main menu appears
The problem occurs before i start something over easyboot menu.
Regards
Posted by balder on Dec. 15 2011,04:07
@schdQuote: The problem occurs before i start something over easyboot menu"
Yes I got the message
But what kind of build is it we are dealing with (WinPE or whatever
)And further more - what is the structure of your EasyBoot-build
Basically; what files or folders (if existing) is in folder 'disk1'
regards balder
Posted by schd on Dec. 15 2011,04:41
Ok, wasn't sure about that ;)But i found out something else:
I took the disk1 folder from a fresh easyboot installation, removed default.ezb and made the iso.
The device=<82> message and delay also occurs, so it has nothing to do with my configuration.
It seems that the new version of easyboot does not like my Dell servers (PowerEdge 1950, PowerEdge R710) ...
Posted by balder on Dec. 15 2011,04:51
@schdQuote: "removed default.ezb and made the iso "
I cannot be to any help if you don't give me some information what kind of build we are dealing with
Is it a kind of WinPE (BartPE or whatever) that is causing you problem
Note: I have my doubt that removing default.ezb should make any changes to the 'right direction'
Sorry I still need information what files or folders you have (and use) in folder 'disk1'
regards balder
Posted by schd on Dec. 15 2011,05:09
balder,when i'm saying i took the disk1 folder from a fresh installation, then install easyboot on your pc to a new location, browse to the disk1 location and you will see, what content it has
i haven't changed or added files, just made the iso over bootmenu.ezb.
Posted by balder on Dec. 15 2011,05:28
@schdQuote: "when i'm saying i took the disk1 folder from a fresh installation..."
Hmm.. You are saying you don't have any files or folders in folder disk1 - with exception of folder ezboot of course - which must be in folder disk1
And when creating this minimal basic build you get errors - correct me if I'm wrong
Okay if this is the case - my guess is that we are dealing with a BIOS-problem
We are now in a position where we need to perform troubleshooting
You could as a work-around, test launching ISO (ISO created by EasyBoot).
This is possible to perform using my scripts
I'm pretty sure you have some USB stick to test with.
Use 'easyboot-usb_v2.script' to make your USB stick bootable and launch ISO created by Easyboot.
In this way we establish a genuine 'real test' what happens if we use ISO instead of boot-file 'ezldr'
It is just an idea to try finding out if this is a 'hardware issue' or if it is a 'BIOS issue'
Though I still think it is related to a 'BIOS issue'
regards balder
Posted by schd on Dec. 15 2011,06:36
Yep, usb stick works. No message or delay occured.But unfortunately i need a iso file for booting easyboot and no usb stick.
So i guess i always have to use a script of yours to generate a working iso?
Posted by balder on Dec. 15 2011,06:44
@schdQuote: "Yep, usb stick works. No message or delay occured."
As expected
Now to the final troubleshooting:
1. Use my script 'easyboot-grub-iso.script' and create ISO-file
2. Use created ISO-file and burn to CD-RW
3. Test and see if ISO works from CD\DVD-reader as well
Note: ISO created by script can be found in folder 'balder\winbuilder_complete' and name to ISO is what you put in text-box in script.
regards balder
Posted by schd on Dec. 15 2011,07:33
Works too.But now i can't start BartPE from EasyBoot menu any more (couldn't find ntldr).
Thanks for your help, but i think i will stay at version 5, where everything is working fine.
Posted by balder on Dec. 15 2011,07:44
@schdQuote: "But now i can't start BartPE from EasyBoot menu any more"
So you did have a WinPE on the root
(folder disk1 is the root for EasyBoot if you wonder)This is no problem
You can still use v6.5 of EasyBoot
I have created an special 'gift' to you
Download zip-file from < HERE >
Extract folder 'myiso' from ZIP-file to the root (C:)
Copy everything you have in folder disk1 to inside of folder 'myiso\iso_root'
Follow instruction in text-file 'myiso\READ_ME.txt' and you are done
This is of high interest as file 'ezldr' is launched by grldr - which could be a solution to other users as well
EDIT:
Another solution could be to simply run the whole ISO of BartPE from RAM!
If ISO-file is reasonable in size (less than 400MB) - it could be an idea to run ISO from RAM!
To run such BartPE-ISO-file from RAM you need to use my script 'easyboot-iso.script'.
Attention! Check 'Run ISO from RAM' in script when you integrate ISO into EasyBoot.
regards balder
Posted by schd on Dec. 16 2011,03:57
Thanks for your efforts 
.myiso:
BartPE works again, but "Device=<82>" and delay reappears.
Due to the result above, I won't test bartpe from ram, don't think that something is changing..
QUOTE
You can still use v6.5 of EasyBoot
I actually meant v5.1.2 ;).
Posted by balder on Dec. 16 2011,04:12
@schdQuote: "BartPE works again, but "Device=<82>" and delay reappears"
Well as it seems to be related to those 'Dell servers' - I guess you better stick to EasyBoot_v5.1.2
Problem is most likely related to BIOS in those machines (post nr; 10 points in that direction)
Sorry not much we can do to solve this issue
balder