开云体育

Yup, I have a file like that. Did you check the SHA256 checksum to verify the download? It will probably be correct, but I've been wary about file downloads for many years now. I'll try writing it to a 32GB USB stick with Balena Etcher v1.5.122 on Win7. Balena says the expanded file being written is 17.2GB. A slow write about 35 minutes, verify another 15 minutes.

My first boot attempt was an old HP 6710b laptop. It is non-UEFI and simply hung while reading the USB. I didn't wait more than a couple minutes. I installed gparted to the Linux Mint 20.3 OS on the laptop. That showed me a 512MB UEFI boot partition and a large protected partition containing the HamPC OS on the USB stick. A later boot attempt went to blank screen and I finally shut it off 15 minutes later.

My second boot attempt was a HP T630 thin client. The first attempt recognized the UEFI and said something about making changes. Several minutes later it went to a blank screen. I let it run for several more minutes then forced shut off. A second boot attempt showed Xbuntu for a while then some boot status lines, and finally back to a blank screen. Several minutes later it finally started showing the GUI screen and then quickly loaded the main window with HamPC logo. I'm guessing the USB stick I'm using is extremely slow but it did finally start and run. This also seems to indicate the OS will boot if used on a UEFI-aware computer but not if non-UEFI......

73, Doug Reed, N0NAS.
?

Is it a 64-bit Intel or AMD (AMD 64) laptop or desktop, where you are trying to run it? Can you follow those steps I sent, to create a USB bootable? (Be careful where "dd" is written to, since you probably don't want to overwrite your bootable disk.)

If it's an AMD or Intel machine, are UEFI and USB Boot enabled?

Not everyone has been able to make HamPC work.

@PaulsSlotHobby19 -

I noticed from your first email that you said you were using Linux Rasbian.

Are you trying to install HamPC (v 1.2, for Intel and AMD Laptops and Desktops) or are you wanting to install HamPi (v 2.0, for Raspberry Pi's)?

The HamPC image (v1.2) is for UEFI-enabled Intel and AMI Laptops and Desktops. I was able to get it to run like this by creating a USB Bootable, from a Linux machine:
* /g/HamPC/message/86

Hi Paul.

I can't tell from your message what the problem is.
Did you download the ISO archive to a Windows box?
I often worry about download errors, but if the file unzips without error the download was correct.
Did you expand the archive file on the Windows box using 7zip, as the instructions say to do?
Did you use a NTFS-formatted drive as the destination for the expanded file?
Did you write the resulting file to a 32GB USB drive using Balena Etcher or Win32 Disk Imager?
If you did all this, then the resulting OS should probably boot.?

When I first downloaded the ISO, I was using a Linux system as you are and I could not get the ISO to work. It made no sense that I couldn't expand the file on Linux since it is using a version of 7zip for Linux. After being advised to follow the directions, I moved the archived file to a Win7 laptop, installed 7zip, verified I had a hard drive formatted as NTFS, and unzipped the file to that drive. My first ISO write attempt was to a "16GB USB drive". It failed as being too small and wouldn't boot, so I tried again with a 32GB drive. It wrote and booted fine.?

What annoyed me most during this process was that none of the programs did a decent job of explaining what the errors were. The programs either worked or gave a vague and general error message. Only one program on Windows finally gave an error message with a hint of the problem. The root cause of my unzip problem on Linux is that the Windows version of 7zip has an extra high-level compression mode that the Linux version does not have. A secondary problem is that the expanded file exceeds the 4GB limit of FAT32 that most USB sticks seem to use. That is why a NTFS-formatted destination was required. The final problem with the 16GB USB drive was because the expanded ISO was originally from a drive just slightly larger than the one I was using. Changing to a 32GB drive solved that problem.

After all that, if you still have problems making it boot, I have to suggest it might be an issue of legacy USB boot drive, or my old favorite of systemd vs isolinux vs grub, now with added UEFI spice. I've never had good luck with boot problems other than trying different hardware. In this case you already. know the hardware works with Linux, so you don't need to fall back to my favorite of using a Knoppix DVD as Proof the hardware can boot Linux. I believe Dave has stopped using that extra compression mode so we should be able to expand future ISOs on Linux. Good luck!

73, Doug Reed, N0NAS.

Hi Paul.

I can't tell from your message what the problem is.
Did you download the ISO archive to a Windows box?
I often worry about download errors, but if the file unzips without error the download was correct.
Did you expand the archive file on the Windows box using 7zip, as the instructions say to do?
Did you use a NTFS-formatted drive as the destination for the expanded file?
Did you write the resulting file to a 32GB USB drive using Balena Etcher or Win32 Disk Imager?
If you did all this, then the resulting OS should probably boot.?

When I first downloaded the ISO, I was using a Linux system as you are and I could not get the ISO to work. It made no sense that I couldn't expand the file on Linux since it is using a version of 7zip for Linux. After being advised to follow the directions, I moved the archived file to a Win7 laptop, installed 7zip, verified I had a hard drive formatted as NTFS, and unzipped the file to that drive. My first ISO write attempt was to a "16GB USB drive". It failed as being too small and wouldn't boot, so I tried again with a 32GB drive. It wrote and booted fine.?

What annoyed me most during this process was that none of the programs did a decent job of explaining what the errors were. The programs either worked or gave a vague and general error message. Only one program on Windows finally gave an error message with a hint of the problem. The root cause of my unzip problem on Linux is that the Windows version of 7zip has an extra high-level compression mode that the Linux version does not have. A secondary problem is that the expanded file exceeds the 4GB limit of FAT32 that most USB sticks seem to use. That is why a NTFS-formatted destination was required. The final problem with the 16GB USB drive was because the expanded ISO was originally from a drive just slightly larger than the one I was using. Changing to a 32GB drive solved that problem.

After all that, if you still have problems making it boot, I have to suggest it might be an issue of legacy USB boot drive, or my old favorite of systemd vs isolinux vs grub, now with added UEFI spice. I've never had good luck with boot problems other than trying different hardware. In this case you already. know the hardware works with Linux, so you don't need to fall back to my favorite of using a Knoppix DVD as Proof the hardware can boot Linux. I believe Dave has stopped using that extra compression mode so we should be able to expand future ISOs on Linux. Good luck!

73, Doug Reed, N0NAS.