* I encountered a curious bug on "pip" command: when I tried to concatenate multiple files using the command format:
pip file1.txt=file2.txt,file3.txt I get the error message:

Exception $03 at user address $0001B1BA. Aborted.

pip works fine otherwise. This error occurs in simulation as well, so it may be a bug in pip command or corrupted distribution disk.
* Beside the strange bug in "pip", most software work fine except gkermit. It just hung.
* Creating a new CF disk is kludgy. I'm not smart enough to have a general solution that reads CP/M68K image (created with cpmtools) on FAT directory and creates a CP/M CF disk. So my solution right now is using cpmtools to create a CP/M68k image, converting it to srecord and serially loading into the RAMdrive location on Tiny68K. With the disk image loaded and CP/M running, I can then copy the files in the RAMdrive into CF. This works well, except loading 2 megabyte disk image into RAM at 38.4K baud takes about 30 minutes. Only need to do this once to create a new CF disk, but it is slow nevertheless.
* Still working on an utility that will copy first 32K byte of memory into the 2nd serial flash. With this utility a new boot serial flash can be created thus allowing boot software update without the need of an external programmer.
* I did all my tests with SanDisk brand of CF which work well. I do have one Transcend brand of CF that read/write FAT16 files correctly on PC but does not read/write CP/M68k files correctly on Tiny68K. I'm concerned that Tiny68K hardware/software may only work with a subset of CF. I'm ordering a batch of Transcend CF and see if I can figure out what the problems may be.
Bill

Hi Bill,
I would love to use the PLCC version of the 68681. I have only found an Advance Information datasheet for the 68681. Although it has a PLCC version of the MC68681FN, I would feel better about creating an Eagle part with the finalized Datasheet. Do you have a finalized MC68681FN Datasheet? Attached is all I can find so far. I've tried several sites. If you or anyone can find a better datasheet, I would be most grateful.

First thing to check is make sure you have a shorting bar in place to enable U5 as the boot serial flash.

Oops... I didn't didn't jumper either of them. That's probably what I did wrong.

Hi Tiny68K Fans,
After much help from Bill troubleshooting my Tiny68K, it all boiled down to a suspicious Transcend 133x 4GB CF Card. It never gave me any good results.
I tried a Transcend 80x 512MB card and it works perfectly. No Errors during the pip with verify command when transferring all files from drive E: to drive A:.
I'm now looking for a good source for some inexpensive as possible Sandisk cards since that is what Bill has successfully tested with. I've looked on ebay
for some good deals. I wish I could buy emass to get the price down. I am interested in getting a few CF cards that work from someone.
I'm using TeraTerm to communicate with my Tiny68K. It can transfer files with Kermit among other protocols. How do I transfer several files at once?
Or do I have to transfer 1 file at a time? I have tried both ways, but I can't seem to get it to work.
Are there any experienced CP/M 68Kers out there to help us all understand how to use CP/M 68K?

• a:pip PIP copies files. The PIP program is over on drive A: I'm in user 1 and on drive D, but I can just refer to A:PIP and CP/M will first look here in 1D:, then in 1A:, and then finally in 0A: where PIP.68K actually lives.
• a:[g0] This is the destination, 0A:. Because I'm now in user 1, if I said a: instead of a:[g0] PIP would copy it to 1A: instead of to 0A:.
• = This separates the destination from the source
• lu.68k The source file to copy from

Are you running at 8MHz right now? I believe you should be able to run at 12MHz.

I have weekend plans that should involve a lot of edit, compile, test cycles so it'll get a decent workout.

• 8 character or less local variable names and #define symbols
• 6 character or less global variable names and function names

What about CPM-68k v1.2? I understand the C source for it is available and the Alcyon C math library is more stable (the floating point library for v1.3 C does not work).

Etchedpixels has both Tiny68K as well as a repurposed SPX MPU board that has CP/M68K installed. I'm hopeful a 68000 FUZIX will become available... soon? Is Ethernet particular important to an useful FUZIX OS? I have a few CS8900 Ethernet controllers I want to try that should fit within the Tiny68K form factor. Alternatively, the 68302 on the repurposed SPX MPU board has a crude SPI interface that maybe sufficiently fast to work with an SPI-to-Ethernet daughterboard.

And CP/M-68K's version of C allows for:

• 8 character or less local variable names and #define symbols
• 6 character or less global variable names and function names

Alcyon C For CP/M-68K. Includes compiler, assembler, linker and libraries: http://www.cpm.z80.de/download/cpm68k1.zip
Floating point library for the 68881 or 68882: [url=http://www.cpm.z80.de/download/lib68881.zip]

Rons-MacBook-Pro:cpm68k1 amp1$ ls
v101	v102	v102a	v103
Rons-MacBook-Pro:cpm68k1 amp1$ cd v103
Rons-MacBook-Pro:v103 amp1$ find . -type f -exec grep -l SSIZE {} \;
./cgen/cgen.h
./cgen/main.c
./cpp/lex.c
./cpp/preproc.h
./icode.h
./parser/expr.c
./parser/lex.c
./parser/parser.h
./parser/symt.c
Rons-MacBook-Pro:v103 amp1$