Topic: ERD Commandar Help
started by: AhrimanSefid
Posted by AhrimanSefid on May 26 2012,03:29I edit ERD Commandar with easy boot and run it ,it stops at this part that picture1 shows and it didn't go to next step and part please help me.
i want it run the next part that picture 3 show for select operating system.
Posted by balder on May 26 2012,06:53@AhrimanSefid
Quote: "I edit ERD Commandar with easy boot and run it ,it stops at this part that picture1 shows and it didn't go to next step and part please help me.
i want it run the next part that picture 3 show for select operating system"
This problem occurs because the network adapter in the computer is not compliant with Recovery Manager.
Therefore, the drivers for the network adapter are not loaded during Recovery Manager startup.
Or put it this way; Your ERD Commander is to old to be used to newer motherboards
This also means , your ERD cannot support NT6-OP-systems (typically; Vista Win7 Win8 etcetera)
If you have a NT5-system installed to hard-disk, ERD certinly would find this OP-system and 'mount it'
In fact, I would say this is a perfectly normal behavior from ERD Commander
Posted by AhrimanSefid on May 26 2012,07:26dear friend picture number 3 as you can see is the original program an it's running without any problem, but 2 other pictures (Picture 1 and 2) they are edited with easyboot, now what should I do? in the original program same as picture number 3 there is a box with this description "select the window installation you want to repair" but in the version I have created with easy boot it's like the picture number 3 and there is no box with the mentioned description. I extracted files from the erd commander to disk1 folder and picked the boot file and used run erd.bif command for launching it as my solution do you have any other way?
Posted by balder on May 26 2012,09:46@AhrimanSefid
Quote: "I extracted files from the erd commander to disk1 folder and picked the boot file and used run erd.bif command for launching it as my solution do you have any other way?"
Sure you can use this method - its okay
Note: however this method only works from CD\DVD-unit and not from USB
But I recommend you to use my script 'easyboot-iso.script' to integrate ERD ISO-file
Note: tick 'Run ISO from RAM' in script - ISO must be run from RAM with a special method that script implement
As a benefitt using this method, you can run ERD from both CD\DVD-unit as from USB and also have several different ERD systems integrated into Easyboot
If you are lucky it works better this way as well
I notice you run Vista system version 6.0.6000
You are recommended to instead use MsDart60 as recovery system (skipping ERD as is not compatible with Vista)
Again I must repeat; you cannot run recovery of a NT6-system using a recovery system like ERD which is based on NT5-system (major difference there)
You need MsDart60 ISO-file
To integrate MsDart60 do it this way:
1. Copy MsDart60 ISO-file to folder EZBOOT
2. Use menu command in EasyBoot menu; run msdart60.iso (or whatever name you use to ISO-file)
3. Only tick 'Joliet' when creating ISO in EasyBoot
This method works from CD\DVD-unit as from USB without problems
Posted by AhrimanSefid on May 27 2012,02:16thanks @balder do you have any link for downloading MsDart60?
also the version I am using is version 5 but it's giving me error. any solution for solving this problem?
Posted by balder on May 27 2012,05:12@AhrimanSefid
Quote: "thanks @balder do you have any link for downloading MsDart60?"
Actually no link because off license agreements
Did you use my script 'easyboot-iso.script' to integrate ERD ISO-file
And I repeat; checking 'Run ISO from RAM' in script - ISO must be run from RAM with a special method that script implement
As a benefit using this method you can run ERD from both CD\DVD-unit as from USB
If you are lucky it works better this way as well
You can create your own rescue CD using this method < HERE >
But I also used Google and found this link < HERE >
Hopefully this can help you
Note: this is only a simplified 'rescue' CD of Vista and not the full MsDart60-ISO-file
By the way, always use your 'friend' Google, before asking around
To integrate ISO into EasyBoot, use tutorial in post nr; 4
Why don't you create your own VistaPE-rescue CD (ISO-file)
1. Download WinBuilder_082 from < HERE >
(Push on the green 'button'-Download in upper right part of window)
2. Create a new folder 'MyWinBuilder' on the root (C:\)
4. Copy downloaded WinBuilder_082.exe to folder 'MyWinBuilder'
5. Double-click to WinBuilder_082.exe and check 'vistape.winbuilder.net'
6. Continue with push on Download to the lower left in WinBuilder window
7. Start your funny trip and create your own personalized VistaPE
Note: you can check win7pe.winbuilder.net or whatever PE-builds you like to create
It takes some time to download the first time - but when done, you are set to create your VistaPE-build (or Win7PE or whatever) whenever you like
Attention! I'm not going to give you any support to this here in EasyBoot forum
However, I do recommend you to join as a member in 'reboot.pro' (create account in upper right corner) < HERE >
Posted by ricfil on Jun. 11 2012,23:40Hello all. Since I´m new to this board and I´m just starting, I would like to thank everyone for the amazing helpfull tutorials around here, which already helped me alot in what I´m trying to do. P.S: Loved the "forum rules: respect other forum members",ehehe . Enought said. From what i´ve read this really seems a great comunity to learn from.
Relating my doubt, I´ve already built other bootable multiboot DVDs (using xboot and the likes), but they all seemed to lack that one bit of "extended" configurability in what concerns adding our personal touch to builds of our "own". I´ve decided to plung into easyboot, as it seems to be one of the most configurable pieces of software out here. The thing is, having almost build my multiboot dvd as I like it(being a computer tech I managed to combine almost all boot cds I need at work into one DVD), the problem being...ERD Commander...arghhh, lol. Since AhrimanSefid started this topic on the same issue I decided not to create a new one, but instead continue using the info on this one.
I started with the dreeded winbom error at boot up. Whenever I uncecked joliet and checked optimize, ERD booted fine but Linux bootloader dependent isos did not. The opossite solved the linux boot isos problem but brought back winbom error in ERD. I decided to give Balder´s scripts a go (pretty good one´s it seems). I used easyboot iso script (load to RAM enabled) and, after creating the iso image, on virtual Box ERD Commander works flawlessly every time I boot it up. The problem is whenever I try to boot ERD on two real PCs (just to be shure), after loading ERD to RAM (which takes a lot of time), on one PC (mine) ERD gives me an error "cannot load setupdd.sys, error code 4", and on the other PC it simply frezzes on a black screen where nothing happens (even after several minutes of wait time...
Any idea someone, of what might be hapening? It is just that one ERD Commander 2007 that is keeping me from burning the final "build" onto a DVD...
Hope someone may help with valuable information, which I pretty much apreciate.
Thanks all. See you
Posted by balder on Jun. 12 2012,01:59@ricfil
Welcome to EasyBoot @ricfil
Quote: "It is just that one ERD Commander 2007 that is keeping me from burning the final "build" onto a DVD"
Unfortunately this is not an unusual scenario regarding ERD-2007
ERD-2007 is getting 'old' comparing to newer motherboards and drivers related to these motherboards.
It would be of an interest to know how old those computers (motherboards ) are
On the other hand, make sure you have enough RAM when using my script to launch ERD (run from RAM).
You need 3X RAM than size of ISO to make sure computer doesn't 'freeze' when loading and run ERD from RAM
Could you please test these solutions:
1. Only integrate ERD and nothing else into EasyBoot (use my script)
2. Test from CD (I use CD-RW to not spoil anything)
3. 'Burn' to USB stick (you must use my script to make ERD work correctly in this case)
Note-1: Loading and launch ERD takes less than 60 seconds from USB (in 'normal' case) - If it takes more time - then motherboard isn't that brand new, which also most likely means, it doesn't support USB-2 speed already from BIOS
Note-2: Most of these problems can also be related to BIOS-problems (or hardware fail)
Quote: "cannot load setupdd.sys, error code 4"
Sounds like a hardware problem to me
Read < HERE >
Posted by ricfil on Jun. 12 2012,14:11Thanks for the quick reply Balder. And the welcome words also.
I will try and create an ERD Commander iso alone and test that out as (using your script) as you pointed.I´l come back and post the results. Relating the motherboard versions, shouldn´t Virtual Box "emulate" hardware based on the physical hardware of the host machine?...Not really into pc emulation a lot... I thought it would.. here goes the set up:
- My PC as got an asus board 2009 model, with I3/5/7 cpu support and DDR3 memory (pretty recent I guess.
- My cousins suports core 2 duo cpus and DDR2 2 memory.
- And I also have an Old 2000s pc with Rambus(RIMMs as oposed to DIMM modules from nowadays) memory on it (only 128MB-which does not allow me to test this stuff out as I wanted).
Relating the 3x memory allocation needed for your scrip. I did not think it needed that much memory . That might be why my cousins pc froze on me (4GB of memory). But still, my machine has got 8GB of memory, my iso has got 3.1 GB, which would be enough for even my pc not having enough memory to run it according to the 3x assumption ...
Anyway, will try the ERD" iso alone" idea. Will post back.
P.S: Ho!,relating the possible hardware issue, I don´t think it might be that as that happened on my machine which as got Windows 7 Pro on it (that issue seems related to XP systems only). Also the system runs pretty stable on me all the time.
Thank you for the interest Balder.
Posted by balder on Jun. 12 2012,14:31@ricfil
Quote: "I did not think it needed that much memory"
I think you may misunderstanding what I mean with '3X RAM than size of ISO'
A 'standard' ERD-2007 ISO-file has the size of 185 MB (or close to at least) - this means (in theory) that you need 512 MB RAM to make sure ERD ( and motherboard) can handle the situation.
In fact it should work with 2X RAM than size of ISO (again in theory)
You are talking Gigabyte of RAM - so there cannot be any problem related to size of RAM in your case
However that 'Old 2000s pc with Rambus' has probably not the 'right configuration' to work correctly in this case2
Finally; the point with 'Burn' to USB stick (you must use my script to make ERD work correctly in this case)' is only for test purpose to see 'what happens'
Posted by ricfil on Jun. 12 2012,15:50Ok. I´m back after some testing. I´ve just tried creating an iso with erd commander only on it using Balders script "easyboot iso". An erro occurs whenever I try to do so. The same error apearde the last time a tryed to run the script on my project (managed to stop that from happenning renaming the iso). This time, even if renaiming only to ERD it comes back with the same error. here goes the error info:
"FileCopy - Failed to copy [%BaseDir%\Temp\newimage\ERD.img] to: [C:\EasyBoot\disk1\ISO\ERD]"
Relating the usb boot thing, that would be my next step (if I managed to create the bootable) DVD which is becoming a hard thing to do
I´ve tried creating a bootable usb with easyboot Balders usb v2 script, but a warning appears saying several usb devices are conected to my pc, and that I need to umplug them. I do have HDDs conected to the pc but they all are disconected from power (only the mouse is usb feed).... kind of stuck in a root right know...
P.S: The ERD Commander iso file is 184 MB large on its own and works flawlessly on VMs and also on every and each computer I throw it at on a single cd... Shouldn´t it behave the same on its own if motherboard issues were to happen?...Strange to say the least. I´ve read more people having the exact same issue with this iso.
Thanks for the help man.
Posted by balder on Jun. 13 2012,03:50@ricfil
Quote: "I´ve read more people having the exact same issue with this iso"
You (hopefully) did read the help-file 'READ_ME.html' in folder 'balder'
If not - please read and watch also to the flash-movie integrated into help-file...
1. Extract folder balder to the root (C:\)
2. Run EasyBoot from the root (C:\) as well
3. Do not have spaces in name to file(s) and folder(s)
4. Turn off virus protection (if used)
5. If run in Win7 - set UAC (User-Account-Control) to lowest level (reboot computer to make change take affect)
Note: all this is described in 'READ_ME.html' (including a link to an flash movie showing how script is used).
Quote: "I´ve tried creating a bootable usb with easyboot Balders usb v2 script"
You don't need my script in this case - use EasyBoot: 'Burn>>Write USB Disk'
However you need to take attention to post nr; 1 < HERE >
Note: 'easyboot Balders usb v2 script' is very handy to use when you must use NTFS as file-system to USB device (Example: run Win7.vhd-file or run Win8 directly from USB)
Quote: "warning appears saying several usb devices are conected to my pc"
As told, you don't need this script at this point, but in future when run script, unplug all USB drives except the one you are preparing to use (USB stick or USB hard drive)
Note1: script is very careful to not destroy data, this means script examines your computers USB inputs, and if find anything 'suspicious' it halts, to avoid any destruction of data to any USB device
Note2: Script is on the other hand clever enough to handle several partitions to your USB device.
Script also always choose the first partition as target (generally the 'boot partition')
USB mouse is not any problem, but have USB printers/Scanners off, to make sure it isn't recognized as an USB device - which really shouldn't be any problem - but some computers do behave strange
But totally disconnect your USB hard disk(s) unit and only have your 'target' USB device plugged into motherboard
Quote: "The ERD Commander iso file is 184 MB"
As expected - shouldn't be any problem to run from RAM
Posted by ricfil on Jun. 13 2012,14:03Hello Balder. Thanks once again for the help. I´ve missed the "run your scripts from the root drive" part ... But I´ve tried this way before and it worked using the script sucessfully Anyway, will try it the correct way this time. Regarding the usb script, regardless of not needing it, I realise it needs all usb cords to be umplugged from the usb ports on the motherboard? Strange it behaves this way, since they are not being feed through the motherboard power, so that should not be a problem... Got that anyway.
Relating the bootable usb, from what I´ve read in the post you´ve mencioned it has a lot to take into consideration to being able to put a bootable usb working correctly (specially changes in commands and the likes). In the mean time, I do not have the time to fiddle with that for as long as I obviously need . Will try the iso script for ERD on his own to see how it goes.
Posted by balder on Jun. 13 2012,14:54@ricfil
Quote: "I do not have the time to fiddle with that for as long as I obviously need "
Yes the USB approach was only to test ERD from a different 'position'
But you can still use 'easyboot-iso.script' to run ERD from RAM, to look for any improvements in its behaviour
Note1: that 'winbom' thing is typical for a missing driver - most likely related to some NET-driver. Do you really need to have the NET-driver up and run, as ERD works okay without it anyway
Note2: when testing in VmWare ERD most likely can find the NET-driver, but this is not the same as when testing in 'reality'
Testing in VmWare is NOT bullet proof
Posted by ricfil on Jun. 13 2012,17:26Hello there balder. Nice tips. I´ve managed to correctly use your iso script using the right "root way" of doing things. My bad Will still try the usb "burn" idea just to see how it goes.
Regarding the testing:
Created both an ERD 2007 iso only and one with all of the other isos I´m trying to compile. On VIrtual Box, all works great-just as before. On real pcs? On my cousins pc, it still frezzes on a black screen endlessly. Tried one other machine but the DVDRW does not even boot (incompatible DVD drive maybe...) On my work machine (the RIMM modules one) the memory is not enough to accuratly test this stuff out. But...on my personal machine ERD...booted fine! Tried also MSDaRT x64 vista and 7 x64 and they also worked great strange the misbehaviour ERD has from machine to machine... (BIOS/firmware version compatibilities maybe?). Anyway, I´ll try this weekend the isos on my girlfriends laptop (1GB Ram-XP installed) to see how it goes... I do not give up that easily. I´ve already burnt my DVDRW a "few" times...
Thanks for all the help and ideas into this stuff balder. I do really apreciatte helpfull people like you.
Take care man.
P.S: Forgote to mencion. I´m afraid the "winbom" error as more to do than the lack off network drivers... As you may see on one of AhRimanSefid printscreens, when the winbom error appears, ERD can NOT detect any installed system on the HDD, (even when you´re booting to a non XP machine, it usually points you that the version you are using is not compatible with the installed/detected version)
In our case, we simply do not have any OS detected and, therefore, cannot continue using the "live environment"(continue button grayed out). I do believe the "evil" Winbow error has more to it than network stuff. And I believe if it had those kind of problems, they would happen even on the ERD Commander cd only (as the hardware would be the culprit here, when ERD tried to interact with the "incompatible" hardware). If it was only that, as I believe you have mencioned around here, the network lack would not be an issue, as ERD tends to serve as an offline utility, rather than an antivirus scanner (which usually needs virus updates/server-network conection).
Posted by balder on Jun. 14 2012,01:40@ricfil
Thank you for your detailed answer including comprising testing of solutions
Quote: "I´m afraid the "winbom" error as more to do than the lack off network drivers"
Yes, unfortunately you seems to have right there
However as told, ERD-2007 is getting old, especially if you compare to MsDart or similar WinPE.
Quote: "BIOS/firmware version compatibilities maybe?"
Not a bad conclusion - most likely you are on the right track there...
Again, thank you for comprising testing - I know by experience how much time and efforts it takes
Posted by ricfil on Jun. 14 2012,20:09Hello once again. Just tried a few more things which I decided to put around here so others can(hopefully) use to try and solve their own ERD 2007 issues.
Managed to test my "easyboot" iso on another machine. Everything seems to work great. Even ERD .Tthe only thing it hapened on that machine was when booting ERD up, if I did not click quickly enough on the "skip network configuration" menu button that appears, the Winbom error appears... Only diference is when closing the error message, ERD stilll boots normally (detects the system on the HDD and all)... It shure seems like some sort of bios conflit when BIOS leads the CPU to put DVD files on RAM... relating each individual machine. Not shure about that though Still, I´m going to test the iso on my girlfriends HP just to have another way of testing it.
Also tested the burn usb option. As expected, some isos do work but others don´t (Acronis True Image, HBCD, ERD and MSDaRTs, etc), which leaves me with an unstable build to my bootable usb. I´m still not ready (low on time) to dig deep on how to properly configure and try to run a bootable usb drive using Easyboot.
Nevertheless, my DVD seems to finally been working great, and that is the most important thing at the moment.
Regarding the ERD dated software. I do understand that aspect Balder, but that System Restore option alone....hum...I keep going back to that feature on XP systems gone berserk!
Finally, would like to thank AhRimanShefid for his post (which lead me to some help) and, obviously, to balder, for your incredible work around here and your amazing availability and knowledge. I´ve already learned a few more tricks to help myself on this bootable journeys!
Thank YOU and take care.
See you around.