I have used search and tried everything I could find in other topics regarding similar problems but nothing helped.
Could somebody please help and say what I am doing wrong.
I also attached my log to the post.
![Attached File](http://reboot.pro/public/style_extra/mime_types/html.gif)
Thank you in advance!
Posted 14 July 2007 - 03:08 PM
Posted 14 July 2007 - 06:45 PM
Posted 14 July 2007 - 07:50 PM
Welcome to the board SkullBurner .
Hopefully someone will be able to look at the log and give some help.
Posted 16 July 2007 - 12:06 AM
Posted 16 July 2007 - 04:44 AM
Posted 16 July 2007 - 10:15 AM
I'm also a bit clueless about this issue - Peter (psc) was involved in this script - maybe he can take a look when his short-vacances finish.
In the meanwhile I would only suggest (not sure if it will make any difference) - to use a shorter path, preferably without spaces.
Sometimes a few scripts don't include quotes around the path names and that can give wrong values under some circunstances. Not sure if this would be your case, but you've asked for ideas..
Maybe it also helps if you read the discussion topic: http://www.boot-land...lity-t1580.html
Good luck and welcome to our community!
Posted 16 July 2007 - 10:56 AM
Posted 16 July 2007 - 03:17 PM
Try this , your SDI_Disk is perhaps too littleThank you for your suggestion. I have tried it and it didn't help. In between I tried also NativePE project which has also one different script to produce boot from ram ISO image but there I have the same problem, normal ISO boots without problems but boot from RAM ISO hangs in the way I have described it. I don't understand it, like there is some course over my Laptop that disables production of RAM Bootable ISOs on it.
Posted 16 July 2007 - 11:02 PM
I've never gave much use for the SDI like technology, wish I could you help further with this..
Posted 17 July 2007 - 02:22 AM
Posted 17 July 2007 - 11:22 AM
@skullburner
Please read this thread:
http://www.boot-land...ista-t2586.html
Posted 17 July 2007 - 11:56 AM
Posted 17 July 2007 - 12:59 PM
Please try with the nativeEx project or NativePE - I remember that thuun has heavily tested this script and Peter himself has joined the talks when developing it along with other members - hopefully these projects are debugged to work as expected..
Posted 17 July 2007 - 08:29 PM
Now I tried NativePE again. First time I tried only the MakeISO script to produce both boot from ram and normal ISO but with this script only the normal ISO was able to boot the boot from ram ISO was not working. Now I tried NativePE again but instead MakeISO script I used make bcdw Multiboot script. Now this is funny, the image made with this script can only boot the boot from ram part of the multiboot ISO the normal boot part stucks at please wait.
This is strange but now I have made some progress because now I have at least one working boot from ram ISO.
I will try now to figure out why this script behaves so strangely perhaps I can make one working script out of other 2 scripts.
Thank you all for helping me to solve this!
Posted 17 July 2007 - 08:43 PM
Hallo SkullBurner, willkommen im Team!
I can reproduce your issue on my system. And that's usually 80% of the solution.
(But tomorrow ...)
BTW: You should never start with ALL scripts selected. Easier and better is to start with some scripts which seem important for you.
If that does not run: It is much easier for the forum to help.
If that runs: Fine, add one or some scripts.
...
Until you have your final constellation.
Peter
Posted 17 July 2007 - 08:50 PM
No need to test! It was just a hint to start with small configs.Thats good so I am not the only one with the problem. Perhaps you can figure out what is the solution, I have tried myself many things also that with only core scripts and many other things but nothing helped.I understand your point about many scripts. I didn't think about it as I have made my first post. Next time I will do it like you have suggested.
Posted 17 July 2007 - 08:55 PM
No need to test! It was just a hint to start with small configs.
With a minimized constellation (no apps, only VirtualBox NIC driver) I still have your issue.
Maybe it depends on W2003 SP2 German.
Tomorrow I do more tests.
Peter
Posted 18 July 2007 - 08:04 AM
ok. I'm going to do further tests with that version.I have US version of 2003 SP2 so I think it is not the issue.
Posted 18 July 2007 - 03:19 PM
It seems that BootSDI has troubles with W2003. See here.
Peter
Posted 18 July 2007 - 03:30 PM
Posted 18 July 2007 - 04:05 PM
Though probably unrelated, please do check this post ( about different 2003 "releases":
http://www.911cd.net...o...20016&st=24
jaclaz
Posted 18 July 2007 - 05:12 PM
It is confusing:I have checked this topic. I think that this could be the source of the problems with at least some of the boot from ram scripts. Most of them use their own setupldr.bin files so could be that this mixing of versions occurs.
Is it possible to find out from which windows version steupldr.bin file is coming from? Perhaps there is some data in the setupldr.bin file that can be read by some hex editor ?
Posted 18 July 2007 - 05:54 PM
It is confusing:
A RAM image built from XP sources started from a W2003 'Master boot' works.
A RAM image built from W2003 sources started from a W2003 'Master boot' does not work.
I'm working on this, but I currently do not yet see the light at the end of the tunnel ...![]()
Some minutes later:
Thanks Jaclaz, I see some light.
When building with W2003 R2 English or German, it works!![]()
Because the *.BIN do not have a version number, I made an upload of the running files to http://www.psc.boot-...Scratch/BootSDI
So you can compare whether you have the correct versions.
Warning: Download of the files is illegal, if you do not have the rights to use them!
Peter
0 members, 0 guests, 0 anonymous users