Re: Help! Filetype $00 problems . . .

[Rubywand <rubywand@swbell.net>]

Randy Shackelford writes ...
> 
> Rubywand <rubywand@swbell.net> wrote:
> 
 ....

> : BLOAD TCHANGE.BIN, T$00, A2048
> 
> : DELETE TCHANGE.BIN
> 
> : BSAVE TCHANGE.BIN, A2048, L15711
> 
> : TCHANGE.BIN should be BRUN-able. BRUN TCHANGE.BIN to start the filetype
> : changer program.
 ....

> That won't work since the files become extended during copying. BASIC gives
> a FILE TYPE MISMATCH error in response to the UNSUPPORTED STORAGE_TYPE error
> coming from the kernel. The way to get the files to work is stripping the
> resource fork, which ProTYPE does.
> 
 ....

     So, ... Hubble is downloading everything-- the SYS 6 diskettes plus tcom
util and TCHANGE.BIN-- to a PC, transferring it to a Mac, and putting it on
ProDOS diskettes which are, then, carried over to a GS! And this results in
files which end up with resource forks tacked on which makes them pretty
useless under ProDOS 8. Messy.

     You mentioned a program named "PC Exchange" which results in resource
forks being tacked on. Is this the standard Mac<-->PC file transfer utility? 
Where does a user get the ProType Mac util which removes the resource forks?

     Could a Mac user make a plain NULL modem connection with a PC (using any
normal Mac telecom program on the Mac side and, say, HyperTerm on the PC
side) and avoid the problem of having resource forks tacked on to every file
transferred?



Rubywand

 

Rubywand