Poking at this more....   the SAVE command is acting weird at any size...  
seems like I've just been lucky saving some of the command files...   I'm going 
to need to do a whole lot more digging and some more learning of CP/M before I 
can get to the bottom of this problem.   ahh, perhaps I need to take a step 
back and do some more diagnostics and testing of the SD read/write routines... 
but that will wait for another day.


From: [email protected]
To: [email protected]
Subject: RE: [N8VEM-S100:5511] CP/M acting weird
Date: Mon, 3 Nov 2014 19:45:52 -0500




Hi guys,

Ok, I'm trying to transfer the standard files to my virtual disk on the SD Card 
(8080 CPU board).

I am using Rich Cini's suggested method of getting the file into memory at 
0x100 (via my monitor's Xmodem routine).
Then warm booting CP/M and doing the SAVE x filename.ext command.

This works fine for files that are 32 blocks or smaller, but when I try a file 
that needs to save 40 blocks, the SAVE command corrupts my directory and 
virtual disk.  

I'm going to poke at it some more, but if anyone has any suggestions, I'd love 
to hear it.

PS. I have tried rewriting my firmware to use a stack in the High ram area, 
just following through on a hunch and previous problem about running out of 
stack space.  I have about 300 bytes of stack space available there, assuming 
CP/M does not change the stack pointer.  But, why should CP/M change the stack 
pointer? the BIOS cold and warm boot sets it according to the adapted Hardware.

Cheers,
Josh

                                          





-- 

You received this message because you are subscribed to the Google Groups 
"N8VEM-S100" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].

For more options, visit https://groups.google.com/d/optout.
                                          

-- 
You received this message because you are subscribed to the Google Groups 
"N8VEM-S100" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to