Bostonman, Yes I think I still have the image. I finally sold this scope because I had an opportunity to get a DSO8104A.? I'm trying to upload everything I have on the 54832 but it's a big file. Whenever it's ready, I'll post the link. For now, this is the content of the C directory (it's not an image, but it might help

By any chance, were you able to find the drive to image? I can't communicate with the SSD in my scope because it has only 44 pins with (what I recently learned) Vcc on pin 41 and 42 and no other power connector.

The USB adapter I have doesn't seem to output 5V on 41 and 42, so I need another adapter to connect 5V to them.

I removed the cover on the SSD. It's only a 44 pin connector without a Molex.

Inside is a small memory card. I plan to buy a card reader to try imaging it.

Any updates on imaging your drive?

Hello Bostonman,

Yeah, here is the link to everything I could find left on my computer, since I don't have the scope anymore. It took forever to upload it!!!?

To communicate with the SSD, try to use an other computer. I know IDE port in modern computer are no longer there. You can buy really cheap adapter from SATA to IDE.

It is possible that your adapter is designed to work with 3.5inch drive that usually had a Molex power connector on the drive. I see that you have a 3.5 to 2.5 inch that requires power supply.?I didn't notice the SSD inside your scope until this morning, it really look like a DIY drive. Since it was booting earlier, I wouldn't modify the HDD yet. I would also try to get the content of the memory card on an other drive.

Maybe the person who sold you the scope still have the mechanical HDD for this scope and could make you an image for your exact scope. Using the image from an other scope is really the last solution because it might bring other problems (bad cal factor, wrong serial number, wrong board version, missing drivers, etc).

The link works, however, the download doesn't seem to be starting.

Does an expiration date/time exist?

The slow reaction might originate from the file size. When I click the link, it says:? I (23G) is too large for Google to scan for viruses. Would you still like to download this file? , assuming that 23G is the file size. It might indeed take almost forever to download this file...
@JulienM: could you please check the actual file size? Thanks!

Chris

It's a 52GB file compress to 23GB. I know it's huge. It took me several hours to upload it.?

I don't remember what is good and what is not. So it's hard for me to select particular things. When I had the unit, I had a backup drive with the original image, but when I sold it, I gave the drive to the buyer. If you can't download it, I can try to upload it an other way. Do you have suggestions?

I'll try downloading it again tonight. I can't use my work laptop because it will encrypt the file.

After sending the message last night, I finally got a message stating it wasn't allowing me to download because of some message stating? it's been accessed and/or downloaded too many times recently; and to try again at another point.

Also, I used a better power connection to that adapter (the 3.5" to 2.5") in case power was intermittent during booting. Unfortunately Windows is still not loading. I keep getting the same message: PXE-E61 media test failure, followed by: PKE-M0F exiting Intel PXE ROM

On Thu, Oct 8, 2020 at 07:16 AM, Bostonman wrote:

After sending the message last night, I finally got a message stating it wasn't allowing me to download because of some message stating? it's been accessed and/or downloaded too many times recently; and to try again at another point.

Ok, give it an other try. If it doesn't work, I'll upload it in smaller part

I feel bad it's not downloading because you're the one helping me and devoting time.

Sometimes nothing starts downloading, other times I get this message:

Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.

开云体育

Hello,

we can use my server. Question is only, how I get the file.

Tam

With best regards
Tam HANNA 

Enjoy electronics? Join 15k7 other followers by visiting the Crazy Electronics Lab at  

Don't worry, I save way more time with this group that I can ever give back, so it's really my pleasure.?

I'll upload it an other way (not zipped, so everything can be download once at a time). I'll post the link when it's ready!

开云体育

Hello,

just cackle, if I can be of use!

Tam

With best regards
Tam HANNA 

Enjoy electronics? Join 15k7 other followers by visiting the Crazy Electronics Lab at  

I'm in the process of downloading it (finally).

Looks like I should get the whole thing. Now I need to get a spare drive and burn it.

One problem: this scope only has a 44-pin adapter (3.5" to 2.5") and the drive only has 44-pins. Power comes in on a breakout connector on the adapter which a tiny connector (that doesn't mate well) provides 5V and ground.

A standard SSD has a SATA connector (?), so I need I need to get a drive that's compatible with the connectors in this scope.

Well you can do it either with a standard IDE drive. Your only challenge will be powering it up. If you have a laptop drive, it will be easier, but you might only have a 3.5 inch drive. 3.5 inch drive can be power up from an other power supply. I did it, it's not clean, but it works (for testing).?

For a permanent solution, I recommend you an SSD. They usually use SATA, so you'll want to get an IDE to SATA interface(). I used them in that scope and others equipements and they work fine. An other big advantage of using standard SATA SSD is that you can plug it into your computer without adapters. If you want to install a newer Windows version, you'll want to be able to swap drives easily! The power supply can be a bit tricky. You'll need a standard power cable from an old power supply and a bit of creativity. I can't remember where I plugged it. I think it was on the front floppy, but I could be wrong.

I'll have to post some pictures again. I don't remember what I posted before, what you read, and what I've already explained.

Basically this scope doesn't have any power cables. It has a CD-ROM, a 3.5" drive, and a 44-pin hard drive. The only power cables are two separate tiny connectors with 5V and ground.

Some good news, I managed to get in touch with the person who owned this before me (I had to dig through old Craig's List emails and try to locate his number). He posted a copy of the original hard drive contents (he no longer has the hard drive), but all I have is a .zip file he created in Linux; and it contains a .dd file.

I'm uncertain how to handle this. I have a laptop with Ubuntu and a Raspberry Pi, but believe I need to take a blank drive and make it a boot drive (I have a Windows program that will do that), but I'm uncertain how to handle the .dd file.

My guess: I create a bootable drive, unzip the .dd. file, and copy/paste all the directories/files onto the bootable drive under the main directory.

On 10/12/20 7:19 PM, Bostonman wrote:

I'll have to post some pictures again. I don't remember what I posted before, what you read, and what I've already explained.
Basically this scope doesn't have any power cables. It has a CD-ROM, a 3.5" drive, and a 44-pin hard drive. The only power cables are two separate tiny connectors with 5V and ground.
Some good news, I managed to get in touch with the person who owned this before me (I had to dig through old Craig's List emails and try to locate his number). He posted a copy of the original hard drive contents (he no longer has the hard drive), but all I have is a .zip file he created in Linux; and it contains a .dd file.
I'm uncertain how to handle this. I have a laptop with Ubuntu and a Raspberry Pi, but believe I need to take a blank drive and make it a boot drive (I have a Windows program that will do that), but I'm uncertain how to handle the .dd file.
My guess: I create a bootable drive, unzip the .dd. file, and copy/paste all the directories/files onto the bootable drive under the main directory.

No.

The file extension of .dd suggests that he created the file using the program "dd". Though some people do this, there is no standard file naming convention for files manipulated with the "dd" program, which simply moves data around between devices and files. It doesn't know about filesystems or data formats or anything else, just raw data to/from devices.

You will need to use dd on your Linux (or other UNIX) system to write that data back to a drive. One potential issue here is that things may go awry if the destination drive is larger than the original drive was; depending on how Windows handles devices and filesystems. It may deal with it, and it may not. (I'm not a Windows guy)

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA

I apologize ahead of time, but I lack experience with Linux, so these commands are confusing me.

The file was downloaded as a .zip, but it contains a file with the extension of .dd. Any 'dd' commands I find seem geared towards using a .iso file to make a bootable drive.

Currently I'm using a Raspberry Pi with a SSD drive connected through a USB adapter.

I looked at the link above, but it doesn't make sense to me. One article stated I need to set the block size, and others have extensively long command lines.

So? I remain baffled at how to handle this.

I'm also not a Linux expert, so I'll let other people speak on that.

For the power, I know there is no Molex cable anywhere. They uses industrial PSU and not standard computer one. So of course, you won't have a ready to use cable to plug in any adapter. But, the rear CD-Rom and floppy must have power since it's a 3.5inch IDE cable (without power) that goes to it. I found an old picture of mine where you can see the power cable. It is possible that the last user lost the adapter board to plug the floppy and drive, but the power cable should still be somewhere in the scope.

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.