Help: UBCD stops after "Loading Boot Sector.. Booting..
Moderators: Icecube, StopSpazzing
Help: UBCD stops after "Loading Boot Sector.. Booting..
Hi guys,
I am having problems getting this nice piece of software to work. I burned the latest iso img using imgburn and the CD actually boots and I can see the menu, BUT
when I choose an application the boot-process stops after "Loading Boot Sector.. Booting..."
Any idea what might be wrong?
Thanks for your support
Rassy
I am having problems getting this nice piece of software to work. I burned the latest iso img using imgburn and the CD actually boots and I can see the menu, BUT
when I choose an application the boot-process stops after "Loading Boot Sector.. Booting..."
Any idea what might be wrong?
Thanks for your support
Rassy
Re: Help: UBCD stops after "Loading Boot Sector.. Booti
Yea , You burned the disk TOO fast...Rassy wrote: Any idea what might be wrong?
viewtopic.php?t=776
Freespire and Puppy Linux user....


Try in one of the virtual machines.Rassy wrote:OK, i did a MD5 checksum test on the downloaded ISO-Image and it equals the published number (4330c7ce679f00963373a768837cf3a0).
So its not about a wrong download.
Any other ideas? I really need to test this harddrive of mine
Thanks for your support
Rassy
For example MS Virtual PC 2007 (seems to be the easiest to use), or VMWare player, with help of that : http://www.easyvmx.com/ (you can't create a virtual machine with VMWare player ~~ ).Rassy wrote:virtual machines? Where do I find those?
There are others but seemed to me they were either a pain to configure ( I'm thinking about qemu ) or very unstable ( now thinking about virtualbox ...).
Hammerite Compendium of Precepts, Regimens and Rules of Conduct, Vol. 113 :
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
The reason is, he's having trouble with the burn. If he uses the ISO in a virtual machine that would eliminate the burn.jason.b.c wrote:Why in the world does he need a virtual machine..?
If the disk he already has dosen't boot...!
I do not agree with Constance regarding VrtualBox. It has NEVER been unstable with any runs that I have used.
VirtualBox is free and still being maintained. If you have problem with it, then report the bug. How else can a program improve without involvement, as in Ultimate Boot disk bug related fixes.
Well I have never been able to install Windows 98 in VirtualBox without several crashes during install - and was never able to finish installing it correctly - though I had no problem with doing it in Virtual PC, using the very same ISO image or real disk in drive.verndog wrote:I do not agree with Constance regarding VrtualBox. It has NEVER been unstable with any runs that I have used.
Hammerite Compendium of Precepts, Regimens and Rules of Conduct, Vol. 113 :
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
QEMU Manager is quite a nice frontend to QEMU. I use it sometimes as an alterative VM for testing.
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Thanks for the info on "easyvmx" ! I never knew it existed. I have both VMware workstation & Player. Player is smaller but can't create virtual machine. I'll try easyvmx.Constance wrote:For example MS Virtual PC 2007 (seems to be the easiest to use), or VMWare player, with help of that : http://www.easyvmx.com/ (you can't create a virtual machine with VMWare player ~~ ).Rassy wrote:virtual machines? Where do I find those?
There are others but seemed to me they were either a pain to configure ( I'm thinking about qemu ) or very unstable ( now thinking about virtualbox ...).
Rassy would benefit from using a VM to check first any mods he makes before burning to CD. It's sooo much faster, and a great quick check.
PS- I never used any virtualmachine with win98.
Nice ^^Victor Chew wrote:QEMU Manager is quite a nice frontend to QEMU. I use it sometimes as an alterative VM for testing.
I'll give it a try :]
Hammerite Compendium of Precepts, Regimens and Rules of Conduct, Vol. 113 :
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
This is a good VM manager! Thanks for info. Very fast indeed. I like the fact you can store on USB pen drive. Small and compact.Victor Chew wrote:QEMU Manager is quite a nice frontend to QEMU. I use it sometimes as an alterative VM for testing.
Why don't you list your PC hardware config, HD-sata,ata, CPU, make,model,etc., DVD/CD info also.Rassy wrote:Hi guys,
I tested the bootcd on a different computer and yes, it works fine there. I am just wondering, whats wrong with my hardware configuration. Is there a list for non-compatible hardware?
Thanks for your support guys
Rassy
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
BTW, did you apply the V4.0.1 patch? I accidentally included an older version of memdisk in V4.0, so wondering whether updating it will help.
You can also try to post the question on the syslinux mailing list, but the discussion there tend to be a lot more technical, so be prepared to eg. regression test on older versions of memdisk until one works, so that the author can identify the changes in the new version that broke on your hardware. This is necessary because the author won't have access to your machine, so he needs to rely on indirect methods to debug.
You can also try to post the question on the syslinux mailing list, but the discussion there tend to be a lot more technical, so be prepared to eg. regression test on older versions of memdisk until one works, so that the author can identify the changes in the new version that broke on your hardware. This is necessary because the author won't have access to your machine, so he needs to rely on indirect methods to debug.