|
Doesn't ANYONE in this group have a copy of the system disks? Once you can boot from anything, things get a lot easier.
Quoting Bostonman <bostonman73@...>:
toggle quoted message
Show quoted text
I was able to burn the image.
First I tried burning it onto an SSD connected to the rear USB through an adapter. Upon powering, the scope seemed to freeze unless I hit 'tab' to bypass the boot screen. At this point I was able to tell BIOS to boot off the USB (I tried all the ones available) and it wouldn't boot.
Today I tried burning the image to a 3.5" IDE. I connected it to the IDE 44-pin cable and powered the drive via an external supply.
In both cases I got the same messages:
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel PXE ROM
Intel (R) Boot Agent Version 4.0.14
PKE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel PXE ROM
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
I'll try turning off something related to PKE in the BIOS, but I'm uncertain why I'm getting this error message. It seems the system isn't seeing the drive, but I've tried the original drive, the SSD, and USB. Also, this issue began after I opened the cover and poked at the cheap hard drive (3.5" to 2.5") adapter; I never tinkered with the BIOS.
|
The WinScopes tend not to be very highly regarded..
-Dave
toggle quoted message
Show quoted text
On 10/15/20 9:32 PM, Bruce wrote: Doesn't ANYONE in this group have a copy of the system disks?? Once you can boot from anything, things get a lot easier.
Quoting Bostonman <bostonman73@...>:
I was able to burn the image.
First I tried burning it onto an SSD connected to the rear USB through an adapter. Upon powering, the scope seemed to freeze unless I hit 'tab' to bypass the boot screen. At this point I was able to tell BIOS to boot off the USB (I tried all the ones available) and it wouldn't boot.
Today I tried burning the image to a 3.5" IDE. I connected it to the IDE 44-pin cable and powered the drive via an external supply.
In both cases I got the same messages:
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel PXE ROM
Intel (R) Boot Agent Version 4.0.14
PKE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel PXE ROM
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
I'll try turning off something related to PKE in the BIOS, but I'm uncertain why I'm getting this error message. It seems the system isn't seeing the drive, but I've tried the original drive, the SSD, and USB. Also, this issue began after I opened the cover and poked at the cheap hard drive (3.5" to 2.5") adapter; I never tinkered with the BIOS.
--
Dave McGuire, AK4HZ
New Kensington, PA
|
The PXE messages are related to a failed Network boot. (People would call this Pixie boot)
Usually in a bios you can set the boot order:
You want floppy ( if available) first,
CD next ( like in a normal PC),
then harddisk,
and last network.
Older Old school PC's would try to always boot from a network, as soon as the PXE ROM was inserted in the network card.
In that case the bios settings would not affect boot order, you would need to remove the network boot ROM first to boot from bios devices.
Remember, this was the case with "real" PC's, not sure how this relates to your machine.
Good luck, stay safe,
Leo
|
I haven't looked for other settings such as Network booting or whatever the term(s) are that I found when searching for this issue, however, I know the boot order is/was for the hard drive.
The 3.5" floppy and CD ROM are disconnected, so I believe I eliminated them from the boot sequence and just had the hard drive. The boot options include several hard drive and USB numbers I think. Maybe HDD1, HDD2, USB-X....
Keep in mind, this booting issue began before I entered BIOS, however, since the issue began, I've changed the boot order several times in hopes to solve the issue.
|
On Fri, Oct 16, 2020 at 03:52 PM, Bostonman wrote:
Keep in mind, this booting issue began before I entered BIOS, however, since the issue began, I've changed the boot order several times in hopes to solve the issue.
Sorry, haven't read all messages in this thread, but did you get your device with these messages showing? In that case it might come from a networked environment, so it is possible the network interface has the PXE bootrom installed. In that case you need to remove that ROM from the network interface, or there may be a jumper/dipswitch to enable/disable network boot on the network interface. If is has a PC like motherboard, you might even (temporarily) remove the network interface. If your machine was working normally (I mean booting from disk like it should), and it stopped booting from disk, there must be something else wrong with your replacement disk, like the bootpartition not being active, etc. There are tools, like? diskpart from Easy?Recovery,?that can do that for you.? Wish I could help you more, Leo
|
Here is what I've tried so far:
The original 44-pin drive that has a mSATA board inside and uses the 3.5" to 2.5" adapter to connect inside the scope to IDE cable
A brand new SSD drive through a 2.5" to 3.5" IDE with a separate Molex power adapter powered by a hard drive USB power supply. This drive has the original drive image the previous owner used to create the mSATA drive (I was able to contact him and he still had the image but not the drive)
A junk 3.5" IDE drive with the image obtained from the previous owner as listed above.
In all three cases, using three different drives, and two different images, the scope gives the same error. I tried the SSD in a junk laptop and it booted to a DOS screen that read something about insufficient memory and then showed a Agilent type large print logo that read: it's safe to shut down now.
I'm uncertain about that error but assume it's because the scope software was trying to boot in a laptop, however, it shows the drive is capable of loading (at I believe this to be the case).
I looked for everything in BIOS related to booting from the network and can't find a single thing. I even used the 'default 1' setting and that didn't help.
This is crazy because all I did was remove the cover, looked at the cheap hard drive adapter, re-seated the cover, discovered the ribbon cable for video slipped out (I wasn't getting any video), re-seated the cable, and then the system failed to boot.
I never went into BIOS prior to this issue, and, should I get this scope to load, still have the 50ohm and self diagnosis issue to deal with - the initial message that began this thread.
|
I'm totally lost.
I've looked through the BIOS numerous times and I can't find a single thing related to PXE or network booting. I also removed (and replaced) the CR2032 battery thus resetting the whole BIOS to default.
Also, I've tried three drives (the original, a 3.5", and a SATA) along with the original image on the original hard drive and the original image the previous owner sent to me that he had.
Is there a possibility the Motherboard is toast even though it sees the hard drive in BIOS?
|
The PXE boot isn¡¯t in the regular BIOS, it is in the network card BIOS. ? David ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of Bostonman
Sent: 21 October 2020 01:07
To: [email protected]
Subject: Re: [HP-Agilent-Keysight-equipment] Agilent 54831M ? I'm totally lost.
I've looked through the BIOS numerous times and I can't find a single thing related to PXE or network booting. I also removed (and replaced) the CR2032 battery thus resetting the whole BIOS to default.
Also, I've tried three drives (the original, a 3.5", and a SATA) along with the original image on the original hard drive and the original image the previous owner sent to me that he had.
Is there a possibility the Motherboard is toast even though it sees the hard drive in BIOS?
|
I don't believe this scope has a network card; it's probably on the Motherboard.
In any case, how do I access/change the network BIOS?
|
If the BIOS sees the disk, but does not try to boot from it,? it must me something with the boot partition not being active.
On older DOS fdisk.exe versions there was a fdisk /MBR option, if I remember correctly.
There are also other tools to activate the partition you want to boot from, using a pc with the disk in question as a second disk connected.
Leo
|
I'm confused.
Did somehow the boot partition get altered? This scope booted fine several times when I first got it and then suddenly didn't.
Keep in mind, this hard drive booted somewhat when I installed it into a laptop. It gave me a message about not enough memory (I'm uncertain why since the scope has 256MB of RAM and my laptop is at least double that; I'm thinking it wanted to see oscilloscope hardware and didn't.
How can I get the boot partition back to normal if the scope won't let me boot from the hard drive?
|
I'm still stuck with this scope not booting.
I've searched and tried everything suggested.
|
can you post pictures of all the POST screens? up to the point that it stops.
try to set the BIOS to "optimized" setting and also I suggest to disable the on board cache memory for now (i dont remember where it is in the BIOS but you can find it easily)
also boot the scope with no GPIB and LAN card (if they exist)
|
I'll post pictures tomorrow.
I have pictures, but they are random at random times, so I'll take a full set from start to finish along with some BIOS menu options.
|
before taking pictures, try to set the BIOS to "optimized" setting and also I suggest to disable the on board cache memory if exists
also try to boot the scope with no GPIB and LAN cards (if they exist)
|
I didn't see an 'optimized' option nor did I see board cache memory.
I forgot to look at whether the LAN is a card or on the motherboard, however, I believe I've tried removing the GPIB but will try again (and the LAN card if it has one).
Attached are several pictures of the boot sequence and various BIOS options/settings..
|
ok the very first thing to note is that your hard drive name is not identified properly, it looks like garbage instead of "SanDisk" that I believe it should have been
so that usually means something is wrong with your drive or the connecting cable has issue. definitely this is the first thing you should look into
click on that hard hard drive and see if the information is correct (space and No. of cylinders and clusters etc....) or they look like garbage
2-you do have a cache setup, under that menu you can disable cache memory?
3- why is HDD inot your first boot device!??
also disable the "Boot Other Device"
4- you can make a bootable win98 CD (or DOS floppy) and try to boot from that and log on and see if you can access your hard drive at all
that would be the first thing I would have done
let us know how it goes
|
I assumed the person who made this drive (or the drive it was cloned from) named it and why the odd name. Also, if I use another drive, such as a WD, I believe it reads WDC......xxxxx
As for the boot order, that's the default, but I've changed the boot order several times Unfortunately it lists HDD1, HDD2, etc... and I don't know which drive is which, however, I've tried all of them including turning off 'boot other device'.
When I removed the mSATA inside this drive (to clone), I was able to view the drive, but I didn't look at the name.
Keep in mind, I've tried another (or maybe two) IDE cables (one for sure was fresh out of a bag - thus never used), and I've tried two other drives; one with an image from someone else.
I fully agree that something is odd with the link between the hard drive and motherboard. Since I've tried one or two other cables, I've ruled out that. I'll try your suggestions.
I THINK at one point I disconnected the hard drive and may have powered it with the IDE cable only on half the pins. Would something like this have blown the motherboard? I just don't remember at what point it stopped booting, but know I never touched the BIOS. I also remember turning off power without shutting down Windows (or maybe while it was booting).
|
the drive name identified by the BIOS is not something that somebody can make up or change it. It is written in the drive's firmware ROM in factory
if it is being identified with garbage name, it is either the drive is bad or the connection. I hardly believe the motherboard chipset is bad. I have never seen that before.
but it can be the motherboard BIOS is having a problem although that is also very rare
|
I'll plug in a different drive and take a picture.
I think the other drive (3.5" IDE) has the image the pervious owner sent to me. So that drive, if anything, should work. The drive I'm using now is the 2.5" with the mSATA card inside - this drive may have been plugged in with only one of the two rows plugged in.
If I remain uncertain, I'll burn the image again and send updates on what I find.
|
Dave McGuire
David C. Partridge