Hi,
You may wish to add x86test to the "CPU Information" section. It is an open-source bootable CPU information tool that supports almost all x86 processors to some extent. I think the simplest way to load it on the UBCD is to stick the zImage version in the isolinux directory and load it with isolinux e.g.
if ($lastKey == key[x]); then isolinux x86test
homepage:
http://www.vortex.prodigynet.co.uk/x86test/
latest zImage binary:
http://www.vortex.prodigynet.co.uk/x86t ... zImage.bin
Thanks
add x86test
Moderators: Icecube, StopSpazzing
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
add x86test
Thanks! I will consider it for the next release.
add x86test
If anyone wants to add x86test themselves I have put slightly fuller instructions here,
http://www.vortex.prodigynet.co.uk/x86t ... ml#booting
http://www.vortex.prodigynet.co.uk/x86t ... ml#booting
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
add x86test
Thanks! I will add this to the list of useful links at the UBCD website.
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Did anyone try this and get it to work with UBCD?
I tried following the instructions at:
http://www.vortex.prodigynet.co.uk/x86t ... ml#booting
I added the following lines to isolinux.cfg:
But "isolinux x86test" merely produces a single dot and hangs. This is on both VMWare and a physical AMD64 machine.
So I verified it by creating the floppy disk using the DOS Installer. This time, it prints "Load x86test", and hangs. I waited for nearly 5 minutes before giving up (since I thought it might be computing the CPU speed or something).
Please help!
I tried following the instructions at:
http://www.vortex.prodigynet.co.uk/x86t ... ml#booting
I added the following lines to isolinux.cfg:
Code: Select all
LABEL x86test
KERNEL x86test.bin
APPEND -
So I verified it by creating the floppy disk using the DOS Installer. This time, it prints "Load x86test", and hangs. I waited for nearly 5 minutes before giving up (since I thought it might be computing the CPU speed or something).
Please help!
add x86test
Hi Victor,
for isolinux you will have to use the zImage version (just the normal binary with 2-sector
zImage header) -- it won't know what to do with a raw binary.
I don't think the KERNEL line is needed if the label is the same as the filename. I just called
it 'x86test' with no extension, but I don't see why that should matter.
I am mostly worried about the installer not working -- the floppy loader 'fatload' has been
very reliable, but it seems to not work for you! It should print "Loading x86test", followed
by a '.' for each file fragment. If there is a read error it will just print a single character
corresponding to the BIOS error number (due to the lack of space for proper error
handling) -- ussually a funny symbol. If it is not printing anything after "Loading x86test",
then this is strange and possibly a signifcant bug in fatload.
Have a look at your floppy lights to check that it's not trying to access the wrong drive or
hanging during a read operation. I've never tried fatload from an ElTorito emulation
(x86test can be loaded directly without an emulation on most BIOSes), but I can't see any
obvious problems. Note fatload will only work from drive 0 (A:), so you may want to try
playing with BIOS setup option for swapping floppy drives for int 0x13 use.
if you were experiencing a bug in x86test itself, you should still see "x86test-0.10a"
printed, as this is done very near the start using ye-olde BIOS calls.
x86test should take less than a second to do everything -- you should see a load of green
text in the BIOS 8x8 font.
if none of this helps then I can add debug output to the zImage setup sector and the very start of x86test to try to see what's going on.
appologies for the problems -- I'd be greatful if you can help fix them!
P.S. ignore the mkisofs options I listed as they seem to cause problems on some BIOSes
-- I'm sure you know more about this than me!
for isolinux you will have to use the zImage version (just the normal binary with 2-sector
zImage header) -- it won't know what to do with a raw binary.
I don't think the KERNEL line is needed if the label is the same as the filename. I just called
it 'x86test' with no extension, but I don't see why that should matter.
I am mostly worried about the installer not working -- the floppy loader 'fatload' has been
very reliable, but it seems to not work for you! It should print "Loading x86test", followed
by a '.' for each file fragment. If there is a read error it will just print a single character
corresponding to the BIOS error number (due to the lack of space for proper error
handling) -- ussually a funny symbol. If it is not printing anything after "Loading x86test",
then this is strange and possibly a signifcant bug in fatload.
Have a look at your floppy lights to check that it's not trying to access the wrong drive or
hanging during a read operation. I've never tried fatload from an ElTorito emulation
(x86test can be loaded directly without an emulation on most BIOSes), but I can't see any
obvious problems. Note fatload will only work from drive 0 (A:), so you may want to try
playing with BIOS setup option for swapping floppy drives for int 0x13 use.
if you were experiencing a bug in x86test itself, you should still see "x86test-0.10a"
printed, as this is done very near the start using ye-olde BIOS calls.
x86test should take less than a second to do everything -- you should see a load of green
text in the BIOS 8x8 font.
if none of this helps then I can add debug output to the zImage setup sector and the very start of x86test to try to see what's going on.
appologies for the problems -- I'd be greatful if you can help fix them!
P.S. ignore the mkisofs options I listed as they seem to cause problems on some BIOSes
-- I'm sure you know more about this than me!
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact: