Search results

Hmmm... you've peeked my curiosity. I located a dump of the ROMS that I found online way back in 2013, and it does indeed have a 0 byte where the 'A' should be, as well as the boot code at $FF00. I also located a dump (not really a dump actually, but rather a terminal emulator capture of the...

So I've just started to rebuild an Atari 800 (original, not an XL), and one thing that I thought would be on the agenda is to replace the 'Option' switch on the power supply board. The key was sticking down and wasn't operating correctly. However, upon disassembling I discovered that the switch...

I probably have a single-board something-or-other that is slower, but my MITS Altair 680b boxes are clocked at 500 khz.

That's quite likely. And it does have a decidedly frontpanelexpress.com 'ish look to it. I dug my Obtronix variation out... here's a pic: As mentioned, the color looks different.

He definitely provided some of his early kits with a cut/drilled/painted panel, as mentioned I have one (and I have one of his kits without the panel as well). But I don't recall ever seeing any of his kits sold with a front panel *with* the labels on it already. The panels he included did not...

At least one of my Obtronix kits has the dress panel. While the color of the listed panel may well be different than what was captured/posted by the seller, the panel that I have has more of a green-ish hue compared to the one in the listing. Perhaps more importantly, mine does not have any...

In Notepad++, go to Edit and then EOL Conversion... if it's 'Windows (CR LF)', select 'Unix (LF)' and then save the document.

I think there's a bit more to it than carriage return/linefeed issues. MS Basic generally* doesn't save your programs in text file format, but rather saves them in a 'tokenized' format (just as the programs exists in memory when typed in). These files are essentially in binary format as a...

One other interesting thing to note... when loading the NABU_5.25_DSDD_CPM_User_Boot.hfe image into the HxC software, it indicates the image is 42 tracks. I would think that it would load 40 tracks.

I think the file that I used was this one: https://vintagecomputer.ca/files/Nabu/disk_images/NABU_5.25_DSDD_CPM_User_Boot.hfe. I wonder if there are some subtle differences between AS and the Kyroflux? EDIT: Actually, it may have been the image in this archive...

For what it's worth, I have not been able to boot the 5.25" gotek image from Grant's site either. Another user that has been testing my cp/m 2.2 hasn't been able to boot it either. It tried re-creating the image, but wasn't successful. Pretty sure there is an issue with it, but the the 3.5"...

The boot ROM (patched or otherwise) is out of the picture once the disk is booted into cp/m. So lock-ups after entering a few commands, or format working occasionally, etc... would suggest that you have a hardware issue, be it with the floppy controller or the NABU itself.

All of the sources that I've seen from DR (that were purported to 'original') used uppercase with the copyright text and all generated error messages. 'Purported' is the operative word here, but I believe that was likely the case, if for no other reason than to maximize compatibility with the...

Here you go, assembled at D000 with BDOS assumed to be at E200 (it's only used for the serialization code).

Good catch, thank you. The assembler I used for that binary is sjasmplus, and I just tried various incantations of the original 'and (not fwfmsk) and 0ffh' instruction and all produce a 0 result. However, changing it to 'and (~ fwfmsk) and 0ffh' as with your code snippet produces the desired...

Not sure if you're a Windows user, but a tool that I've used for years and find invaluable is a hex editor called HxD. It has a binary compare feature, among other things.

BDOS starts with 6 bytes that represent the serial number, then a jump to the entry point (over 8 bytes/4 words that collectively is referred to as the 'parameter block'... they appear to be pointers to various error routines).

The attached BDOS binary was assembled at origin $E200 with BIOS assumed to be at $FC00. I use this code with my cp/m 2.2 implementation and it works fine, but if you discover something odd please let me know.

Per my post here, once the HFE is converted to a raw image all track format data is lost, only the sector 'user data' is retained. Converting it back to a HFE file won't recreate the lost data that is required by the NABU.

Yes, the disk based format utility (and I assume the cycle 1 format in the disk utilities menu) will format the hfe image file just fine on the Gotek. Copying ccp.com and cpm3.sys to the formatted image will result in a bootable image. The format utility supports all three of the boot image...