From: Simon Cooke <[EMAIL PROTECTED]> > > Edwin > > OK... Gotta ask... What's your day job, Edwin?
Obviously not a C programmer :-) My Cs not that bad either But All I I could find in the tape.c was whenever blocks are over 64K they are not saved at all. So I was thinking maybe I'm missing something. > If you can write assembler like a demon, and not C, then we need to fix that. >I'm willing to help in any way I can. I can use a little help on getting started again. At the Time when I did my screenviewer. I started out with with Borland C++ 5 to which I had access But It took ages to build a project on my old system and I had problems with the GUI getting to work. On the TAP part. An Idea I have myself to handle large blocks is to split large data blocks>65535 in to two or more blocks. On loading blocks with a size of 65535 will continue loading with the next block(s) In this way ba TAP file will stay ZX compatible. As far as I know SAM and ZX header length are not the same so when a spectrum(emu) tries to load a SAM header there will be a checksum error and it will try the next part in tap file. Correct me if I'm wrong. dsk is the standard for SAM files and it is a convenient one. But TAP could have some advantages like there is no 'useless'data stored like in some dsk have garbage in file gaps and unused sectors. They could be very small in size but also can also be easely over 800K :-) Edwin
