On 3.3 any program loading with diskemu may not load, but it it machine dependent. I have a couple of programs I load with diskemu, and there is grub and Windows Memory Diagnostic Test - all load fine on 2 of my older machines, but none will load on my newest machine. It doesn't even get out of the menu - just a screen flash and back to the menu. All other programs using isolinux and memdisk load just fine.

I have no idea what is different on those machines that could cause this symptom. I'll report more if I see something that would help.

...On 3.3 any program loading with diskemu may not load, but it it machine dependent. I have a couple of programs I load with diskemu, and there is grub and Windows Memory Diagnostic Test - all load fine on 2 of my older machines, but none will load on my newest machine. It doesn't even get out of the menu - just a screen flash and back to the menu. .

Various 'loading' messages flashed up on the screen briefly. Then the screen cleared, and I got two backslashes, one under the other.
Under those came two horizontal lines, about 6 inches long, one under the other and close together, ending in a forward slash.

That's the "expected" result. Windiag isn't compatible with memdisk andwill result in the behaviour you encountered, which is why diskemu isused to boot Windiag.

This proves that there's no media error, but it also seems to indicatethat both diskemu and bcdw wouldn't work with Windiag on your machine.

Any other suggestions?

I've downloaded ubcd32 and the Windows Memory diagnostic works fine on that. Also, I have another computer on which I can't get ubcd33 to boot at all, but ubcd32 is fine. But other people have mentioned booting difficulties with ubcd33.

I can report further complicated behavior. I have 2 computers that work just fine, and 3 that don't work using diskemu.

On the ones that don't work using diskemu, they also give "disk error" when using Victor's suggestion of
dropping to the console [F10], and type:
> bcdw boot /images/windiag.img

Ok, same as Allan saw. However when I use the above command on my two unique images that won't work with diskemu, they work just fine. It's a pretty subtle problem, I guess - both machine dependent and program dependent.

Hi, I use ubcd with Windows Memory Diagnostic Allmost every day,and I have noticed the following behaviour.On mainboards with chipsets VIA works just fine.On mainboards with intel 865 and ich5and above (945 and so) does not work at all.it boots normally, then when i press F1 everything is as expected,but when i press F7 (Disaster Struck ).This example below,is on a mainboard Asus p5p800 SE with 865 and ich5 LGA + celeron 341 (2930MHz) FSB 533.
Error: CD-ROM emulator is already active.
[Command: diskemu] [Line: 73.2] [File: launch.scn]
/boot/menus>

Now,i can assure you that it was a first boot, there is no way the emulator was already active.!!;)

Maybe the developers of ubcd can understand exactly what happens,and maybe fix this issue on the next version.For any questions or further informations about this,post here or PM me.Thx[/img]

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum