Windows Memory Diagnostic

Report new bugs here, or look at known issues of current and previous releases of UBCD.

Moderators: Icecube, StopSpazzing

Locked
Message
Author
Allan Jones
Posts: 6
Joined: Wed Jun 22, 2005 4:21 am

Windows Memory Diagnostic

#1 Post by Allan Jones » Wed Jun 22, 2005 4:31 am

Hello,

Apologies if this has been mentioned before.

I've got version 3.3 of UBCD. When I try to launch Windows memory Diagnostic from Mainboard Tools, nothing happens.

I assume something is supposed to happen? Or does nothing happening mean that a check has been done and everything's fine?

Best wishes

Allan

Victor Chew
Posts: 1368
Joined: Mon Feb 21, 2005 10:59 pm
Contact:

Windows Memory Diagnostic

#2 Post by Victor Chew » Wed Jun 22, 2005 6:09 pm

No, you should be brought to a full screen where it displays information
about what is being tested. How about other memtest tools such as
MemTest86 or MemTest86+? Do they work?

Allan Jones
Posts: 6
Joined: Wed Jun 22, 2005 4:21 am

#3 Post by Allan Jones » Thu Jun 23, 2005 3:11 am

No, you should be brought to a full screen where it displays information
about what is being tested. How about other memtest tools such as
MemTest86 or MemTest86+? Do they work?
MemTest86, MemTest86+ and a random selection of other items work. Windows Memory Diagnostic does not.

I have downloaded both the Basic and the Full versions of UBCD and burned them to CD. I get the same result with both versions.

Regards

Allan[/quote]

Michelle
Posts: 3
Joined: Thu Mar 10, 2005 7:43 pm

#4 Post by Michelle » Thu Jun 23, 2005 3:23 am

Victor, I have a similar problem and have examined it further.

Here is what I have discovered, but no solution.

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.

Allan Jones
Posts: 6
Joined: Wed Jun 22, 2005 4:21 am

#5 Post by Allan Jones » Thu Jun 23, 2005 4:08 am

Michelle wrote:Victor, I have a similar problem and have examined it further.

...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. .
Yes that's it. You don't get out of the main menu.

Allan

Victor Chew
Posts: 1368
Joined: Mon Feb 21, 2005 10:59 pm
Contact:

Windows Memory Diagnostic

#6 Post by Victor Chew » Thu Jun 23, 2005 7:45 pm

How about dropping to the console [F10], and type:

> bcdw boot /images/windiag.img

Allan Jones
Posts: 6
Joined: Wed Jun 22, 2005 4:21 am

Re: Windows Memory Diagnostic

#7 Post by Allan Jones » Thu Jun 23, 2005 10:56 pm

Victor Chew wrote:How about dropping to the console [F10], and type:

> bcdw boot /images/windiag.img

That gave me:

Bootable CD Wizard v2.0a1 Copyright (c) 2004 by Alex Kopylov
Loading...
Disk I/O error


and nothing further. I tried a couple of times.

Allan

Victor Chew
Posts: 1368
Joined: Mon Feb 21, 2005 10:59 pm
Contact:

#8 Post by Victor Chew » Sun Jun 26, 2005 5:59 pm

Hmm... could you try "memdisk /images/windiag.img" at the console?

If that doesn't work too, I am out of ideas. Sorry.

Allan Jones
Posts: 6
Joined: Wed Jun 22, 2005 4:21 am

#9 Post by Allan Jones » Mon Jun 27, 2005 2:47 am

Victor Chew wrote:Hmm... could you try "memdisk /images/windiag.img" at the console?

If that doesn't work too, I am out of ideas. Sorry.
That was interesting. Here's what happened.

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.

After that, nothing further.

Regards

Allan

Victor Chew
Posts: 1368
Joined: Mon Feb 21, 2005 10:59 pm
Contact:

Windows Memory Diagnostic

#10 Post by Victor Chew » Mon Jun 27, 2005 5:58 pm

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

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

Any other suggestions?

Allan Jones
Posts: 6
Joined: Wed Jun 22, 2005 4:21 am

Re: Windows Memory Diagnostic

#11 Post by Allan Jones » Tue Jun 28, 2005 3:12 am

Victor Chew wrote:That's the "expected" result. Windiag isn't compatible with memdisk and
will result in the behaviour you encountered, which is why diskemu is
used to boot Windiag.

This proves that there's no media error, but it also seems to indicate
that 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.

Regards

Allan

Michelle
Posts: 3
Joined: Thu Mar 10, 2005 7:43 pm

#12 Post by Michelle » Wed Jun 29, 2005 5:17 pm

Sorry for the delay.

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.

zxspectrum
Posts: 4
Joined: Tue Mar 21, 2006 8:29 am

Problems with Windows memory diagnostic

#13 Post by zxspectrum » Thu Jun 08, 2006 4:50 am

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]

Locked