oaknut-hfe
HFE (HxC Floppy Emulator) disc-image support for the oaknut family of packages.
An HFE file records each track of a floppy disc as the raw bitstream the drive head delivers. It is the native format of the HxC and Gotek floppy emulators and a common output of preservation capture hardware such as the Greaseweazle. Because it sits below the sector level, an HFE image keeps everything an original disc carries, including the non-standard sector IDs, deliberate CRC errors, deleted-data marks and extra tracks that copy protection relies on.
This package reads HFE v1 and v3 images, decodes their FM and MFM tracks into sectors, and flattens a decoded disc into the logical sector image that the oaknut filesystems read.
Usage
Every disc command that reads an image opens an HFE file as the sector
image decoded from it:
disc ls 'Dunjunz_D1S1.hfe:$'
disc export Dunjunz_D1S1.hfe dunjunz/
The disc hfe commands look below the sector level:
disc hfe info Dunjunz_D1S1.hfe # header and decoded layout
disc hfe sectors --anomalies Dunjunz_D1S1.hfe # what protection put there
disc hfe flatten Dunjunz_D1S1.hfe Dunjunz_D1S1.ssd
From Python:
from oaknut.hfe import HFEImage, analyse, decode_image, flatten
disc = decode_image(HFEImage.from_filepath("Dunjunz_D1S1.hfe"))
flat = flatten(disc) # flat.data is the .ssd image
for finding in analyse(disc, flat.layout):
if finding.anomalous:
print(finding.track, finding.side, finding.remarks)
Status
Pre-alpha, read-only.
Installation
uv add oaknut-hfe
License
MIT — see LICENSE.
Metadata
Release files for oaknut-hfe 13.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| oaknut_hfe-13.6.1.tar.gz | 29.6 kB | Without provenance | Details for oaknut_hfe-13.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| oaknut_hfe-13.6.1-py3-none-any.whl | Python 3 | none | any | Details for oaknut_hfe-13.6.1-py3-none-any.whl |
Total release size: 54.9 kB
Release files / oaknut_hfe-13.6.1.tar.gz
| Download URL | oaknut_hfe-13.6.1.tar.gz |
|---|---|
| Size | 29.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28c274b19999e9ba35407e4cb98b7d7617ad02d6dd9b90ead96d51d9959b8d81
|
|
BLAKE2b-256 checksum How to use checksums |
d65b916f25bc327e3e3dee3257eee14352c05f0808498baa50860ae8da498fda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / oaknut_hfe-13.6.1-py3-none-any.whl
| Download URL | oaknut_hfe-13.6.1-py3-none-any.whl |
|---|---|
| Size | 25.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af285babc8c29ba13ff5f341680fb4fed61ec4a00d3237cd87621ce36b9eb596
|
|
BLAKE2b-256 checksum How to use checksums |
c6297047984a8b3bae97fdba1914b70e3baf6e475c11bbcb4b512ee36f7ffe8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for oaknut-hfe 13.6.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.