VOGONS


First post, by analog_programmer

User metadata
Rank Oldbie
Rank
Oldbie

This is a simple CLI tool I wrote for splitting (interlace), merging (deinterlace) and slicing (cutting in half, if one and the same BIOS ROM-dump file is concatenated) of those old BIOS ROM dump files. It's self explanatory (no need for readme.txt, help.txt, etc.) and may be handy to someone else.

The tool can split (interlace) ROM-dump files if their size is 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144, 524288, 1048576, 2097152 or 4194304 bytes (4 kbit up to 32 Mbit). It also can merge (deinterlace) "low" and "high" ROM-dump files it their size is 256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144, 524288, 1048576 or 2097152 bytes in size (2 kbit up to 16 Mbit). The tool checks if generated files already exists, if files are already opened and for file naming redundancies.

In the latest version 1.5 I added an option /C to slice (cut) in half those ROM-dump files (4 kbit up to 32 Mbit in size) created by concatenation of one and the same BIOS ROM-dump file. Mind that this operation checks every pair of read bytes before they're written, so it's slow. /C (slice) is not same as /S (split interlace)!

The attachment ROM-SM15_usage.jpg is no longer available

There's no option for binary concatenation of two ROM-dump files into one, as you may use "copy /b file1+file2 file3" (in DOS and windows) or "cat file1 file2 > file3" (in Linux) commands for this purpose.

EDIT: Attachments for the tool are removed, due to forum's administration request. There were some false positive malware reports, so no Linux and windows x86 and x64 versions of ROM-SM will be available in the future. New DOS-only version will come soon....

Last edited by analog_programmer on 2026-10-07, 17:22. Edited 4 times in total.

The word Idiot refers to a person with many ideas, especially stupid and harmful ideas.
This world goes south since everything's run by financiers and economists.
This isn't voice chat, yet some people overusing online communications talk and hear voices.

Reply 1 of 1, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

Thanks, I'd use a Windows x64 binary actually, since I'm on that OS when downloading BIOSes and writing them with the programmer.

Cheers!

Turbo XT 12MHz, EGA, MFM HDD
Intel 386 DX-33, Speedstar 24X, SB 1.5, 1x CD
Intel 486 DX2-66, CL5428 VLB, SBPro 2, 2x CD
IBM BlueLightning 100MHz, CL5428, SB16, 4x CD
Intel Pentium 90, Matrox Millenium 2, SB16, 4x CD
HP Z400, Xeon 3.46GHz, YMF-744, RTX2060