Converting D64 to T64 ?
Saber Rider
Hi!
I have some D64 - Diskfiles with Demos on them. Now I want to try them out on
C64 Alive (which has much better sync). How can I tear the files from the diskimage
to single tape files ? Is there a utility that is able to handle this ?
cu, Ray
========\|/====================================================================
_ (\ -0- ( Rainer F. Froemming /\_/\_~_/\~ ( sites:
-{_\ /|\ ( Starnberg, BY/Neil Pryde/F2 WCE275 \ \ ( Ammer Lk.
-_(__\ ( froe...@informatik.tu-muenchen.de ^^^^^^^^^^^^ ( Starnberg Lk.
_{i__\ ( P100/16MB/1.2Gig Alpina PRO LX/DX ( Lago di Garda
~++^++++++~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Greg Alt
getting them onto a real live C64?
Ok, first of all, my impression is that D64 is an image of a whole disk,
directory and all. T64 is "tape format" which means that it is a single
file from a tape. Now, is "tape format" just another name for a single
file? Meaning that I can just copy foo.t64 over to a 1541 disk drive,
(giving it an appropriate name) and it would work without modifications?
Ok, now, to transfer files to a C64, I see two options:
1) use a program like x1541 to transfer them directly from my PC
2) put the files on my account at school, and call up with my C64 1200 baud
modem and dowload them one by one.
What I would like to know is how would I do either of these with a d64 or t64
image? Would I need to do some conversion beforehand for either format?
Thanks. Also, if the FAQ writers are reading this, please add any info
to the FAQ, as I don't believe the FAQ is very clear on this issue.
Greg
--
Videogames, Unicycling, and Anarchism: http://www.cs.utah.edu/~galt/
Jouko Valta
In article <48b1mv$o...@magus.cs.utah.edu> ga...@diamonds.cs.utah.edu (Greg Alt) writes:
Greg> Could someone answer a few questions for me about D64 and
Greg> T64 formats and getting them onto a real live C64?
...
Greg> Thanks. Also, if the FAQ writers are reading this, please
Greg> add any info to the FAQ, as I don't believe the FAQ is very
Greg> clear on this issue.
As far as I know, the FAQ maintainer is very busy in writing that ...
X64 version 0.3 PL 1 8 November 1995
Special features in x64 emulation
and
Emulator File Conversions
Introduction to the X64 system on the hardware and compability point
of view.
All details are subject to change.
8. FILE COMPABILITY
Commodore 64 ROM Images
X64 ROM Image Set
C64S Romcode
Mac64 ROM Resource File
A64 romcode
Commodore 128 ROM Images
X64 Ram File
X64 Snapshot [draft]
Disk Image Files
X64 Disk File
*.D64 disk File
Tape Image Files
*.T64 tape image
Program File
CBM Files
*.P00
SID Music Files
Playsid
CBM Archive formats
11. FILE CONVERSIONS
11.1 Text Files
11.2 Emulator Archives
11.2.1 Disks
11.2.2 Tapes
11.3 CBM Archives
12. TRANSFER
12.1 CD-ROM
12.2 CBM
12.3 Amiga
12.4 PC
12.4.1 What you'll need
12.4.2 PC Transfer Cable
12.4.3 PC Transfer Programs
12.5 CBM Networking
13. FURTHER READING
13.1 X64 Documents
13.2 Other Documents
13.3 FAQs
13.4 Internet Resources
13.5 Commodore Manuals
------------------------------------------------------------------------------
8. FILE COMPABILITY
X64 provides complete backward compability, but the implementation of new
operating modes requires system files that are not interchangeable. There
must be separate RAM and ROM (including modules) images for each program.
The RAM expansion and disk images are the same.
However, as there are several emulators for different platforms, all files
cannot be made directly usable. Utilities to convert those back into CBM
binary exist already. Check out the comp.emulators.cbm FAQ for more info.
Below is description of the most common file formats. some of them are
supported, the others are just for reference.
Commodore 64 ROM Images
X64 ROM Image Set
The ROM images are recognized by their names, 'basic' and 'kernel'.
These files are searched in the Project Directory, which defaults to "C64".
For x64 they are 8192 bytes long each, containing the binary data of
the original ROMs of a machine from C64 series. The default load address
in the beginning of the files is allowed, and skipped when reading the
file. Character ROM image is not used.
One can use many of the different Kernel versions via '-revision' option
on command line. Once the kernel is loaded, it's patched to the desired
version.
Altough any of the original C64 kernels can be used, this does NOT apply to
the third-party products. README tells more about this subject.
NOTE:
The ROMs _MUST_ be for the same machine as the emulator you're using is.
They cannot be interchanged because e.g the memory management and I/O are
completely different on each machine.
C64S Romcode
The file called 'romcode.c64' contains copies of total 4 ROMs, which
makes it 36864 bytes long.
The kernel image in this file is modified, and thus it cannod be used
for any other purposes than for C64S emulator.
Offset Bytes Description
0 16384 disk drive rom
16384 4096 chargen rom
20480 8192 basic rom
28672 8192 kernel rom
Mac64 ROM Resource File
In additon to miscellaneouas data, the 6510.rsrc file contains the C64 ROM
images. In version 0.4 they seem to be located in the following places:
$0422 - $2421 BASIC
$342a - $5429 KERNEL
A64 romcode
Since A64 uses kernel emulator instead of actually running the 6502 ML,
the A64 ROM files only contain some lookup tables, not the real ROM data.
Commodore 128 ROM Images
X128 ROM Image Set
The ROM images are recognized by their names, 'basic' and 'kernel'.
These files are searched in the Project Directory, which defaults to "C128".
For x128 they are 36864 and 8192 bytes long respectively, containing the
binary data of the original ROMs of a machine from C128 series. The default
load address in the beginning of the files is allowed, and skipped when
reading the file. Character ROM image is not used.
X64 Ram File Total Size: RAMSIZE + 4103
Upon startup x64 searches for a file called "ram", containing the RAM
memory from a previous run. If one is not available, a cold start (the
normal power boot-up) is required. A ram image from clean run (not eg.
a freezed demo) is, however a vital resource for advanced use of x64,
since it makes possible to skip the RESET sequence.
The inbuilt monitor treats this file somewhat differently, since it
also saves and restores the state of I/O area as well as the 6510
registers. That makes it possible to use so called snapshot images.
Offset Bytes Description
0 RAMSIZE contents of the RAM
RAMSIZE 4096 I/O area with shadows
7 CPU Registers: PC (LO/HI), AC, XR, YR, PS, SP
Draft for X64 snapshot format -- Preliminary data.
Another file format with exact snapshot has been planned, but it's
not fully defined yet. Below is a briefing.
Offset Bytes Description
0 6 ID Code
6 2 Reserved
8 2 Header version
10 1 Snapshot version
11 1 Snapshot type (device number etc)
12 20 Pointers (HI/LO)
32 8 Configuration bit masks
40 40 CPUs
80 48 OS/Kernel info
128 128+ Flags for peripherals, special features, etc.
256+ RAMSIZE Contents of the RAM
? 4096 I/O area
the rest 16384, (32768) or 65536 bytes of VDC RAM in C128 dump
Note: This RAM format draft description is shown only for information, and
thus it should not be used as any reference yet!
Disk Image Files
X64 Disk File Total Size: 174912
Offset Bytes Description
0 4 Magic Header: 'C', 0x15, 0x41, 0x64
4 2 Image Format Version:
C1541 Version Major
C1541 Version Minor
6 1 Disk Type:
0 = 1540
1 = 1541 (Default)
2 = 1542
3 = 1551
4 = 1570
5 = 1571
6 = 1572
8 = 1581
16 = 2031,4031
17 = 2040,3040
18 = 2041
24 = 4040
32 = 8050
33 = 8060
34 = 8061
48 = SFD 1001
49 = 8250
50 = 8280
7 1 Max Tracks:
35 (for 1541)
8 1 First Track on the Second Side
0 = single sided
9 1 Error Data Flag
10 22 Unused, must be 00
32 31 Disk Image Description (in ASCII or ISO Latin/1)
63 1 00
64 683 (or 768) disk sectors with 256 bytes each
xxxx #Blocks Error Data Bytes for each Block
For descriptions longer than the above 31 characters, put them in a file on
the disk image.
*.D64 Disk File Total Size: Different sizes
The C64S disk images consist of only the binary data for sectors and
optional error data block in the end.
They can be converted into the right format with c1541 via -cr option.
Size Description
174848 35 tracks
175531 35 tracks + 683 bytes error information
196608 40 tracks
197376 40 tracks + 768 bytes error information
206080? 42 tracks
42 tracks + 802 bytes error information
See "File Conversions" section for details in converting these formats.
Proposed New .D64 Format [ Draft - May 1995 ]
This is the proposal for a new D64 file format. The extension should
be changed to D69 or something to avoid mixing with the old format.
Advantages over the old format:
- supports any number of formatted tracks
- supports half tracks
- supports GCR coded tracks
- supports compressed tracks
RLE decompression is fast, the files remain zippable
LZW decompression is slower but tighter, also needs some memory
- supports write protection flag (no dos messing necessary any more)
- users can atach info text
- does NOT support multidisk images, as it is not practical from the
emulator's point of view
- open for future extension
Please email any suggestions to: mi...@ferlin.fer.uni-lj.si
[File header]
Offset, Size, Info
0, 14 sign: "New D64 File", 0, 1A
14, 2 file type (lo/hi)
0x0100 = 01.00
16, 24 user name
40, 4 offset of info text (0 = no info attached)
44, 1 contents type
0 = empty (invalid!)
1 = 1541 formatted disk
2..255 = reserved
45, 1 write protected
0 = no
1 = yes
46, 2 number of track entries
normal 1541 disk: 88 entries, used entries: 0, 2, 4,
... 66, 68
48, 16 reserved
xx, 8*n track entries (n = number of track entries)
xx, xx track data (for each track)
[Track entry]
Offset, Size, Info
0, 1 track type
0 = empty
1 = simple, decoded sectors
2 = simple with error info, decoded sectors + read codes
3 = RLE coded sectors + read codes
4 = LZW coded sectors + read codes
5 = GCR, raw 1541 coded data
6..255 = reserved
1, 1 type data
type 0: reserved (0)
type 1,2,3,4: number of sectors in track
type 5: reserved (0)
2, 2 track data size
4, 4 file offset of track data
[RLE coding]
initial magic byte MB = $BD
initial data = 0
unpacking input -> output
data <> MB -> data
MB 01 -> MB, MB = MB + $13
MB 02 -> MB MB
MB nn -> nn * last data (nn = 0 equals nn = 256)
[LZW coding]
the coding is similar to GIF coding
4096 dictionary entries
the first 256 entries are byte equivalents
when the dictionary is full it is cleared immediately (no clear codes)
[GCR coding]
the coding is the same as used by 1541 internally
[New D64 handling strategy]
- the emulator must be able to read all track types
- any track can be saved anywhere within the file
- byte coded tracks are saved in type 2 when changed
- GCR coded tracks are saved in type 5 when changed
- an external utility is provided to pack/unpack/optimize D64 files
Tape Image Files Total Size: Varies
*.t64 tape image
X64 does NOT use any tape images, but c1541 can be used to copy to a
disk image files from *.t64 tape images that follow this structure:
Offset Bytes Description
0 64 byte Tape Record:
0 32 Tape description
32 2 Tape version: $0100
34 2 Max number of files, in LO/HI
36 2 Number of existing files, in LO/HI
38 2 -
40 24 User description
64+n*32 32 byte Directory Slots for each file:
+0 1 Slot allocation flag:
00 = free entry
01 = normal tape file
02..FF = memory snapshots
+1 1 File type
+2 2 Start address in C64 memory, in LO/HI
+4 2 End address in C64 memory, in LO/HI
+6 2 -
+8 4 File start address on the image, in LO/HI
+12 4 -
+16 16 C64 filename
Program File Total Size: Varies
CBM Files
X64 uses the standars CBM program files containing load address in
the first two bytes.
*.P00, *.S00, etc.
This is program file for the 64NEU/PC64. These files will be supported on x64
version 0.3.2 and later. To extract the original, remove the first 26 bytes.
Offset Bytes Description
0 8 String "C64File" terminated by 00.
8 17 Original C64 Filename.
25 1 Record size for REL files.
26 varies Original file
SID Music Files
Playsid
From: 3sch...@rzdspc63.informatik.uni-hamburg.de (Michael Schwendt)
There is no documentation about the PSID files in SIDPLAY.DOC !!!
But this C structure should help.
/* */
/* PlaySid 'single-file' header support */
/* Copyright (C) 1994,95 Michael Schwendt */
/* All rights reserved. */
/* */
typedef signed char byte;
typedef signed short int word;
typedef signed long int dword;
typedef unsigned char ubyte;
typedef unsigned short int uword;
typedef unsigned long int udword;
struct psid_hdr {
char id[4]; /* 'PSID' */
ubyte version, versionlo /* 0001 oder 0002 */
ubyte datahi, datalo; /* 16-bit offset to binary data in file */
ubyte loadhi, loadlo; /* 16-bit C64 address to load file at */
ubyte inithi, initlo; /* 16-bit C64 address of init subroutine */
ubyte playhi, playlo; /* 16-bit C64 address of play subroutine */
ubyte songshi, songslo; /* number of songs */
ubyte starthi, startlo; /* start song (1-256 !!) */
ubyte speedhihi, speedhilo,
speedlohi, speedlolo; /* 32-bit speed info (0=50 Hz, 1=60 Hz/timer */
char name[32]; /* ASCII-strings, NULL-terminated ? */
char author[32];
char copyright[32];
/* only version 2+ */
uword flags; /* Sidplayer song 0=No, NZ=Yes */
udword reserved;
};
CBM Archive Formats
Complete list is available in the comp.sys.cbm General FAQ.
From: Bruce Gingery <br...@TotSysSoft.com>
Date: 10 May 1995 14:22:51 GMT
an ".sfx" file is USUALLY a self-extracting archive.
This extension is CURRENTLY being used also by Mac users
for a self-extracting .hqx or any self extracting Mac archive.
It is also the self-extracting .LZH written by Chris Smeets.
and should work either on a C=64 or C=128-in-128-mode.
an ".sda" file is either an older "SDN"(sm) file description
from the Software Distribution Network on Fido and other modem
nets, or a self-extracting archive either from Q-Link or from
Chris Smeets' Commodore ARC program. Should extract on a C64
by running it, (or on a C128 in 64 mode).
an ".lzh" file MAY be extracted (if the sfx header matches)
by pre-appending the operational extraction code from a Smeets
SFX archive, or MAY be extractable with his lharc compatible tools.
This was originally a DOS 8+3 filename supporting format - an
extension from Lzari's LZS archive format, but has since been
extended to utilize any of THREE header formats, probably only
the first of which is supported on C= (last I checked).
'C' source is freely available on the net to handle ALL of the
LZH format archives and headers. The only SFX compression that
I've seen supported is -LH1-, but then I haven't been well C=
connected in some time.
Type-3 headers are the best - as they can include extension
segments to handle ANY filesystem's specifics.
.lha is the Amiga defacto standard for .lzh and can USUALLY
be handled the same way, but uses Type-3 headers and usually
contains an ".info" file.
.ARC is either a Commodore archive or a PK/SEA style archive
using LZW compression and creation of new tools to handle it
are likely to run into the Unisys patent problems if distributed
other than for free. CSARC should handle the DOS style versions
created by CXARC (forget the spelling on it) or by arca, ARC.EXE
(System Enhancement Associates) or PKArc which supposedly is not
still around because of an old lawsuit.
.ZIP is a file created by PKZIP or one of its clones - there
MAY be tools for C64/128 for them. My AV package will VIEW
the archive headers if you can find it, but will only tell you
what's contained, not extract the files
.tgz is a Unix "tar" file compressed with GZip. Not positive
where you'd find either for C64/128 but the source code for both
is freely available on the net. This is identical to .tar.gz
.tar.Z (or .taZ) is a Unix "tar" file compressed with Unix
"compress", virtually identical to .tgz except that the compression
is like ARC.
.lnx is a Lynx/Links file (not to be confused with the WWW
browser of the same "Lynx" name). Essentially it is a series
of CBM files concatinated together by having their last block
pointer changed, and a header stuffed on the front... no compression.
------------------------------------------------------------------------------
9. PROGRAMMING / CONVERTING PROGRAMS
------------------------------------------------------------------------------
9.1 Program file format conversions
P00 -> CBM binary dd bs=1 skip=26 if=FILE.P00 of=file
Ascii text -> BASIC petcat -w2 file.txt > file.bas
------------------------------------------------------------------------------
9.2 Listing Basic Programs
BASIC to SEQ or ASCII
The natural way
If you still have your CBM computer or are now using an emulator, just "print"
a listing to a disk file and use that.
load"program",8
open2,8,2,"0:listing,s,w"
cmd2
list
print#2
close2
this will create a seq file named filename (you may substitute any
legal filename here)
Note that in the 64's BASIC 2.0 anything on a line after `list' is ignored,
so if if you want to contatenate the lines above, you'll have to break after
"list" and start with "print#2" on a new line. Unfortunately, that means
that the disk file will have a blank line and "ready." after the listing.
That's not necessary in the 128's BASIC 7.0. A 128 could have the entire
string of commands on line line (and can avoid writing "ready." to the disk).
If you use print#8,"";:close8 instead of just print#8:close8
you'll avoid one more blank line in the disk file. I don't remember, sorry,
whether print#8;:close8 will work.
Also note the common mistake omitting the print# command (needed to unlisten
the destination device after the cmd command). That can leave BASIC in a very
confused state; the print# is indispensable.
It is possible to get a sequential file of a BASIC program using some word
processors, like The Write Stuff. See your word processor manual for details.
You can load it into TWS format, and any TWS text file can be converted to Pet
ASCII sequential.
Emulators
If you have no 64 anymore, there are 'disk-2-disk' for the Amiga, and 'petcat'
(petcat-2.00.tar.gz) for Unix/Atari ST that will make the conversion.
Or, if you insist in writing your own program, there is a list of BASIC token
codes at ftp.oulu.fi:pub/cbm/docs/cbm_basic_tokens.
Don't forget that CBM uses special characters for cursor control, etc. and
they won't translate properly without a special program - like petcat - to
convert them to comments e.g. <CURSOR RIGHT>, etc.
------------------------------------------------------------------------------
11. FILE CONVERSIONS
Converting files, mainly in D64 format, for other systems is certainly one
of the most discussed subject on comp.{emulators,sys}.cbm newsgroups.
Below are brief instructions for the conversions you may need, to help you
in using X64.
11.1 Text Files
converting text
Newsgroups: comp.sys.cbm
Subject: Re: transfering GEOS files to my PC
Date: Sun, 17 Sep 95 23:47:51 -0500
I hate to dash your hopes, but you cannot use GEOS formatted disks in a PC
clone drive, either. There is, however, a solution which I have used in
transferring GeoWrite files from my C128 at home to Lotus AmiPro on my '486
at the office[
(1) Convert the GeoWrite document to True ASCII using WrongIsWrite 8.1
in GEOS. You will lose some of the control codes, but the text will remain
essentially the same, requiring very little text formatting on your PC word
processor.
(2) Transfer the ASCII files from a CBM-formatted disk to an IBM-formatted
disk using LRR128 (freeware) or Big Blue Reader (commercial ware).
I do this frequently, and it works well for me.
---------------------------------------------------------------------------
John M. Williams ___ ___/ / / ___/ theen...@delphi.com
Newsgroups: comp.sys.cbm
Subject: Re: file problem???
Date: 18 Oct 1995 22:51:21 GMT
Unix files use a LF character (ASCII 10, hex $0A) to indicate the end
of a line. Commodores use a CR character (ASCII 13, hex $0D). PC's
and some other oeprating systems use a CR followed by an LF.
When you download a file from a Unix host to a Commodore, the LF
characters are probably being ignored, so it appears to be all one
line. However if you convert all the $0A bytes to $0D you may find it
is fine.
--Bill.
From: ism...@CAM.ORG (Ismael Cordeiro)
Brian Heyboer (bjhe...@space.honeywell.com) wrote:
> And for those transferring to/from other systems, Apples (][-series and Macs)
> use a CR as an end of line and Amigas use a LF.
CP/M uses CR-LF as eol.
Ismael
* Unix
tr '\015A-Za-z\301-\332\\\|\[\{\]\}' '\012a-zA-ZA-Z\|\\\{\[\}\]'
or
tr '\015A-Za-z\\\|\[\{\]\}' '\012a-zA-Z\|\\\{\[\}\]'
* Petcat (Unix/Atari ST/DOS)
This program converts your SEQ files as well as expands tokenized
C64/128 BASIC programs into 7-bit ASCII text. Unprintable characters
can be shown as hexadecimal codes in parenthesis, via `-c' option.
It is also possible to convert programs from ascii listings into
tokenized basic v2.0, v3.5, v4.0, v7.0 or simon's basic programs. This
program also replaces certain control code names with the actual codes.
Runs on UNIX or Atari ST.
* Gnylf (C64)
From: tr...@marvin.df.lth.se (Linus Walleij)
Newsgroups: comp.sys.cbm
Subject: Re: ASCII TO PETSCII CONVERSION: HOW TO ????
Date: 11 Oct 1995 19:41:35 GMT
In article <milocco-1110...@mac-linac-1.elettra.trieste.it>,
Andrea Milocco <mil...@elettra.trieste.it> wrote:
>I would like to find out a prog in basic for the C64 to convert ASCII text
>to PETSCII.
I made a program called GNYLF V1.1 which converts the following formats:
1. Microsoft RTF Rich Text Format
2. PETSCII
3. IBM-ASCII
4. UNIX (ISO) ASCII
5. Screen Codes
6. Writers Choice (WP)
7. Mini Office II (WP)
8. My own metatext format
80-columns are reformatted to 40-columns and vice versa. Note that this
converter is for text only, so "ASCII-ART" and charts of any kind will
look like rubbish.
Back and forth any way you like. This program will be released on the new
Triad warez disk in a few days. I will also mail it to comp.binaries.cbm
and put it on the Triad FTP. Check this space for announcement in a few!
If you want to be 100% sure to get this tool, then mail me and I'll drop
a copy in uuencoded mail at release date. This goes for all interested
dudes out there.
And ofcourse this is 100% assembler and 100% freeware. (adhere Stallman!)
Linus Walleij aka King Fisher
tr...@df.lth.se | http://www.df.lth.se/~triad |
* CBMASC.EXE (DOS)
Converts CBM text files to ASCII.
-----------------------------------------------------------
From: Alan Jones <alan....@qcs.org>
Newsgroups: comp.sys.cbm
Subject: Re: GEOS Postscript
Date: Thu, 21 Sep 1995 14:13:00 GMT
Someone asked how to get GEOS Postscript output onto a disk file.
Maurice replyed that CMD's Collette Utilites Disk is needed.
GEOPublish is the only software I know of that will generate Postscript
output from a C64/128, and someday I may need to do this. GeoPublish
only sends the Postscript commands through the RS232C (user) port at up
to 9600 bps. It would seem to be simple to capture the Postscript data
stream with another computer using a terminal program and a null modem
connection. I would try capturing with ACEterm, saving to a 1581 disk,
and transfering to MS-DOS format with Little Red Reader (using an REU).
If you have an IBM PC you should be able to use it to receive the file
more directly. Has anyone actually tried this method?
------------------------------------------------------------------------------
11.2 Emulator Archives
List Archive Contents
fvcbm
ftp://ftp.wimsey.com/pub/msdos/misc/fvcbm20.zip
fvcbm displays a listing of contents for most CBM and Emulator
archive types:
ARC230 (ARC),
Self-extracting ARC230 (SDA),
Lynx,
CS-DOS (LZH),
Self-extracting CS-DOS (SFX),
PC64 emulator files (R/S/U/P00),
Emulator tape images (T64),
Emulator disk images (D64 and X64), including 1541 and 1581 disk types.
DIR64
DIR64.EXE works similar to the DOS dir command, but goes into D64 and T64
files and lists their contents. It also lists the PC64/P00 files with their
full 16 char name. To get a complete listing of all your C64 programs, type
dir64 c:\ /s >c64.dir
11.2.1 Disks
D64 -> X64 disk c1541 -cr <new> <IMAGE.D64>
X64 disk -> D64 dd bs=1 skip=64 if=<old> of=<IMAGE.D64>
c64util.zip (NOT c64utils.zip) in frodo.hiof.no:/pub/c64/emulators contains a pair
of tiny command-line operated programs to (1) list the .d64's directory and
number the files on the disk image, and (2) to export a given file from the
image (that's where you need to know the number given by the first program)
to raw P64 format. You can then make a .t64 by importing the raw file to
a new tape in c64s10. This process is, obviously, annoyingly inefficient
and cannot be automated using batch files.
D64 -> T64
From: msal...@ccnet.com
Newsgroups: comp.emulators.cbm
Subject: Anyone in need of D642T64 util?
Date: 27 Sep 1995 22:24:24 -0700
Hey all c64 emu fans out there, I just wrote a simple (but complex of
course) util to convert single files from D64s into T64s, and it'll even
create a loader if it requires a sys address. It runs in 50-line VGA.
You put the name of the D64 on the commandline, and from there it is all
interactive. It surely saved me a helluva lot of time converting some
stuff. Just post here if you're interested, then I could put in on FTP
--
I uploaded D642T64.ZIP to frodo (frodo.hiof.no). It should be put in the
utils directory soon.
- Evan -
convert .D64 & .t64 files back to CBM 64 files
The 170K represents the exact,
byte for byte image of a 1541 format disk (including the directory info,
sector links, and all that other housekeeping stuff). There are three ways
to get the *.D64 files back onto regular Commodore disks:
DT64 by Kevin Brisley runs under DOS and performs many functions on .t64 and
.d64 images including extracting files from the images back to raw c64 files.
It also copies and moves files between .t64, .d64 and raw images, allows
you to format blank .t64 and .d64 images and more.
DT64C (DOS/UNIX) from the same author includes a number of utilities (source
included) that perform all of the functions of DT64.
C64Neu formats (.P00, .S00) will be supported in the next version.
You can get them from the following sites:
watson.mbb.sfu.ca: /c64/emulator/dt64_10.zip (DOS)
or /c64/emulator/dt64c_10.zip (UNIX w/source)
wuarchive.wustl.edu: /pub/MSDOS_UPLOADS/emulators/c64/dt64_10.zip
or /pub/MSDOS_UPLOADS/emulators/c64/dt64c_10.zip
a) Use the program dfiler to read the d64
file off one disk and write out the 1541 image on another. This requires
two drives - one large enough to hold the image (has to be bigger than a
1541 to fit), and one 1541 or 1571 to accept the output. Slow (author
was working on speeding it up), but works.
b) Use a program running under Unix to change *.d64 image file into
four Commodore 1!*zip, 2!*zip, 3!*zip, 4!*zip files. These are NOT the
regular *.zip files, but a C64/C128 specific method of generating a
disk image. (Broken into four pieces.) There is a Commodore utility
called ZIPCODE to create/dissolve this format. This can work with only
one disk drive.
c) Use a Unix based program to extract the individual files from the
*.D64 image file. Then transfer the files as usual. This is difficult
to do on complicated, multi-file packages.
From: dis...@news.dorsai.org (Paul Lieberman)
Subject: Re: HELP! How do I transfer .d64 and .t64 files to a CBM disk?
blistyx (us...@portal.dx.net) wrote:
: I have a program that is supposed to work on a C64 to extract
: D64 images to a disk. I have not used it because it is easier for me to
: extract the files on my IBM and send them to my C64 while I sleep. :)
: If you want, I'll UUencode a copy and post it to this newsgroup. However,
: you will need ALOT of disk space. That D64 image file is larger than a
: single side of a 1541. So you will need MINIMUM, a 1571 drive formatted
: on both sides for 1328 blocks, or a 1581. One of these two will have to
: hold the D64 file while its contents are written to the C64. I have been
: told that this program runs EXTREMELY slow....if you guys are still
It's slow, but it works. I happen to have a uuencoded copy in my home
directory. It's short, so here it is:
**************************************************************************
* Paul Lieberman "From out of the depths of Brooklyn..." *
* dis...@dorsai.org -- p.lie...@genie.geis.com *
**************************************************************************
From: David Belter <dbe...@delphi.com>
>Where can I get a program to convert .D64 files to run on my Commodore?
Ok, heres the lastest version of my Program for converting .D64 files,
it requires 2 drives (or REU with RamDos and 1 drive) and one of the drives
has to have the ability to hold the .D64 file .ie '71 or '81.
It's still slow but I am working on that problem. I can't seem to generate the
correct Sector Interleaves for each zone.
So here's a program by David Belter <dbe...@delphi.com>
begin 644 dfiler0.56
<uuencoded_portion_removed>
J````````````````````````````````````````````````````````
`
end
------------------------------------------------------------------------------
From: ez1...@nyssa.swt.edu (Bo)
Subject: Re: HELP! How do I transfer .d64 and .t64 files to a CBM disk?
Date: 21 Oct 95 17:02:41 CDT
Question then.. do you have some manner to get programs which you
receive from ftp sights onto a commodore disk which has a higher capacity
than a 1541 disk?
That is, do you have 1. a) Modem & ability to download from your account or
or b) Big Blue Reader, to xfer from a pc to c64/128
or c) modem connection with a pc for xfers
and 2. 1581, 1571, or CMD device which can hold more
than 170k files.
and 3. some minor programming ability
and 4. Access to a PC, or pkunzip at least.
If so, then you can retreive the files as follows:
Log on to the above site, and change to the games directory,
then go into the /a directory and find the alter ego zipped program.
(probably 'alterego.zip'). Then 'get' the file in 'bin' format and transfer
it to to some sort of pc compatible with pkunzip on it. Unzip the file: at
this point, a series of "*.d64" files should issue forth, one for each alter
ego disk.
Nows the hard part. You have to transfer the .d64 files onto some
sort of commodore disk. Each .d64 file is about 174k (689 blocks), which is
why they won't fit on a single 1541 disk. Copy the d64 files onto a series
of 1581 or 1571 disks so you can transfer them to 1541 format. I have
all my files on a pc hard drive, and transfer them to 1581 disks with
Big Blue Reader. But you do this however you can.
Now, type the following program into your c64 computer and save it:
10 input"drives",d1,d2:ifd1=d2ord1<7ord2<7then10
20 input"enter filename of d64 file";f$
30 open4,d1,15:open3,d1,3,f$+",s,r":input#4,e
40 ife>0thenclose3:open3,d1,3,f$+",p,r":input#4,e:ifethenclose3:close4:end
50 open1,d2,15,"i0":open2,d2,2,"#":t=1:s=0:gosub100
60 fort=1to17:fors=0to20:gosub100:next:next
70 fort=18to24:fors=0to18:gosub100:next:next
80 fort=25to30:fors=0to17:gosub100:next:next
90 fort=31to25:fors=0to16:gosub100:next:next:close3:close4:close2:close1:end
100 b1$="":b2$=""
110 fori=0to9:get#3,a$:b1$=b1$+chr$(asc(a$+chr$(0))):next
120 fori=10to255:get#3,a$:b2$=b2$+chr$(asc(a$+chr$(0))):next
130 print#1,"b-p";2;0:print#1,"u2:";2;0;t;s
140 fori=0to9:print#2,mid$(b1$,i+1,1);:next
150 fori=10to255:print#2,mid$(b2$,i-9,1);:next
160 print"b-p";2;0:return
When you run the program, the first drive given will be the drive on which
the *.d64 file is found (not a 1541), while the second drive will be a
1541 with a blank, PRE-FORMATTED disk. Run this program for each *.d64
file, for each disk.
The above program was adapted from memory of the c128 program I wrote,
and it SHOULD work. If it doesn't, let me know and I'll debug it.
Zipcode -> .D64
ftp://frodo.hiof.no/pub/c64/utils/zip2d64.zip
ftp://lennon.engr.wisc.edu/pub/c64/utils/zip2d64.zip
T64/D64 conversion utilities:
d64utils.zip, d64util.zip, and 64uti5.zip.
.D64 -> Zipcode
disk2zip converts D64 to C64 Zipcode file.
Unt64 and Und64 will convert .t64 and .d64 files into normal C64 PRG files.
Available on Aminet/pub/misc/emu, and frodo.hiof.no.
Trans64 (DOS) will extract file from a d64 or t64 image. The file must comply
with the 8.3 FAT limitation, unless you can run it under OS/2 on HPFS. You
are given the opportunity to rename the file.
Converters etc. WWW page:
http://www.cfn.cs.dal.ca/Services/PDA/commodore.html
For Infocom games, there is a program that lets you take .d64 and translate
it into a .dat file that any z-code intrepreter can read. z-code is the
format for all infocom text adventures, and interpreters are available for
macs (and most platforms). the files needed can be found at
ftp://ftp.gmd.de/if-archive/.
Here is (uuencoded) little program by Rick Kephart for use to dissolve
.d64 files. You need at least one 1571 (or bigger) drive, since the whole
thing won't fit on a 1541.
It transfers a .d64 file on Drive#9 to a *formatted* disk in Drive#8.
begin 600 d64
<uuencoded_portion_removed>
end
------------------------------------------------------------------------------
Compressed D64 ?
From: jls...@uci.edu (Johnathon Suker)
Newsgroups: comp.emulators.cbm
Subject: Re: 64 emulation on mac?
Date: Tue, 22 Nov 1994 10:04:38 -0800
> To convert C64 files to mac, I first have to use a program that converts them
> to ibm dos format, then put the ibm disk in the mac.
> if I could just pop my 64 disks into the mac this would save lots o time.
I am in the process of writing a program for the Mac which does just that.
I will allow you to use standard .d64 image types (that are used on with
both the IBM emulators and the Mac64 emulator) and manipulate them on the
Mac (basically a DT64 program for the Macintosh), however, it will also
convert many of the standard Commodore 64 wordprocessor formats (Easy
Script, Speedscript, PaperClip).
The initial featurs will be coping files to and from diskimage to the Mac
in both binary and ASCII form ( ASCII form will have the conversions done
automatically).
Future features (implemented after the inital version is being banged on
by interested parties, unless I get real productive) will include direct
copying between images, deleting, and renameing files).
Anyone interested in beta copying or wanting more information can send me
email and I will inform you when it is completed (or if you wish to help
test, when it is in beta).
Johnathon Suker University of California, Irvine
Office of the Dean
School of Physical Sciences jls...@uci.edu
Double-spaced floppies
For *.D64 files dblespace gives nearly 2:1 compression.
To make, type: dblspace /compress a:
------------------------------------------------------------------------------
11.2.2 Tapes
T64 -> X64 disk c1541 -t <disk> <TAPE.T64>
(To create the disk, use c1541 -f <disk> 'name,id')
T64 -> P00 T64toP00.exe (Bundled with pc64.)
Converts all *.T64 files in a directory
to *.P00 files
prg -> T64 maketape.arj
------------------------------------------------------------------------------
11.3 CBM Archives
Suffix Format
.arc ARC
.ark Arkive
.lnx Lynx
.sda Self Dissolving ARC
http://www.funet.fi/pub/cbm/archiving/cbmconvert-1.1.tar.gz
ftp://ftp.funet.fi:/pub/cbm/archiving/cbmconvert-1.1.tar.gz
.??? ???
Commodore 64/128 Compression Software
*************************************
UU-Xfer 64/128
An all-purpose UU-decoder/encoder for the 64/128. Necessary for use with files on
CFN that might be encoded. Graphics on archives usually use this encoding.
Documentation is included. Runs on all Commodore 64/128 computers.
o UU-Xfer 2.7K bytes
o UU-Xfer.Docs 2.7K bytes
ZipCode 64
This unpacking program will allow you to unzip any program that may require it on
CFN and any other archive. Read and print the 'ZipCode.Readme' and
'1_Zip.Readme' files before proceeding for instruction how to properly use this
program. Runs on all Commodore 64/128 computers.
o ZipCode 11K bytes
o ZipCode.Readme 400 bytes
o 1_Zip.Readme 2K bytes
o 1_Zip 37K bytes
o 2_Zip 41K bytes
o 3_Zip 36K bytes
o 4_Zip 39K bytes
o Zip Collection 15K bytes
PKUnZip64 V1.01
Packing and unpacking program for the 64/128 system. Read and print the
'PKUnZip.Readme' file for instructions on installation and use of this program.
o PKUnZip64.Readme.sfx 5.5K bytes
o PKUnZip64.sfx 12K bytes
Decomp 64/128
A series of 5 decompression and conversion programs. Read and print the
'Decomp.txt' file for instructions.
o Decomp.txt 966 bytes
o Decomp.lzh 30K bytes
o Decomp2.lzh 21K bytes
LZHTOSFX Conversion Program.
A program necessary for converting some archives from the MS-DOS style of
encoding (.lzh) to the self-dissolving archives (.sfx) of the 64/128 series of
computers. Read and print 'LZHTOSFX.Readme' file for instructions.
o LZHTOSFX.Readme 3.0K bytes
o LZHTOSFX.sfx bytes
C64S_ARC V1.1B
Necessary for converting .d64 (disk) and .t64 (tape) files over to C64 files for use of
the Commodore 64/128. Use the 'ZipCode' program to unpack and run for on-line
instructions. Most game archives use these filetypes for storage and conversion is
impossible without this program.
o C64S_arc.zip 72K bytes
Trans64 (C64 Emulation Converter)
Actually a program for PCs, it allows the PC user to run many .d64 (disk) and .t64
(tape) programs, emulating a C64. For those former C64 owners who are feeling
nostalic over the old 64s, they can now relive the magic. Use PKZip to expand.
o Trans64.zip 8.8K bytes
[ dissolving Lynxes on PC64 ]
make sure LYNX was set to drive 8 for reading, drive 9 for writing...
some unpacked .lnx'es on my harddrive, and I just
created a new .d64 empty disk with C64S, then (from DOS) copied it 6-7 times
so I had lots (right.. :) of free disks on my hard drive. Then from C64s
imported the .lnx files into the disks (keeping on filling until I got an
error (disk full) on each).
After that, just started Lynx (from a tape image, but that's, ahem, irrelevant)
and dissolved all files in a row.
Convert Commodore ZIP format to .D64
If you have
1!whatever
2!whatever
3!whatever
4!whatever
then ignore the ?!'s and use 'zip2d64 whatever' or something...
ZIP2D64 whatever file.d64
This would write a .D64 file named "FILE.D64" with the contents of
the 4 ZIPPED files you used
(do NOT type the 1! etc crap! Just name and extension)
Dissolving big ZipCode files
Usually this will not be any problem.
ZipCode will ask you to put in the disk with 4!xxxx on it. In fact you could
putALL the files on seperate disk and Zipcode would ask for each part.
What you do is put the 4! file on a separate disk, and when it says it can't
find it, just put the disk in that has it. The disk that is being written too
will be fine (it doesn't have to be '71/'81 unless it was zipped with that version and specifically says so). This is just a case of the archive being
bigger than the actual data.
Subject: Re: Unpacking .LZH/.LHA files in C64?
: How to uncompress .LHA/.LZH archives in my C64? I've tried LHX64
: unpacker, but I get errors in every file - when I transfer those
: into my PC and unpack, no errors.
It sounds like the archives are LHA version 5. CS-DOS's LHX only does
version 1, so I'd guess LHX64 is the same way. If you can list the
contents of the archive, it should tell if they are version 1 or 5.
The only utility I've found for unpacking LHAv5 is a CP/M utility called
PMEXT.COM, which is part of the PMAUTOAE.COM package, available at
ccnga.
--
The only problem there is the Commodore names. CP/M cannot handle
file names that do not conform to the DOS naming convention.
SO.....just get the source for LZH, compile it on your UNIX
account....and have fun. Do not forget to set the compress
switch to -o (old style -LH1-).
> A 128 in CPM mode can disolve some of them like LH-1, LH-5, IBM .arc,
> and .arj. (We can't yet disolve PKzip 2.04g (or .gz), Unix Compress
> (.Z), or Mac formats.)
From: "Jeremia J.S" <sky...@dds.nl>
Newsgroups: comp.emulators.cbm
Subject: Re: Corrupt GZ files on http://www.cling.gu.se/~cl3polof/64games/
Date: Tue, 10 Oct 1995 19:32:33 +0100 (MET)
Do not use WinZip, I always use the DOS mode. Type:
gzip -dN filename.gz
(small d for decompression, capital N to retrieve the old and real
extension name, see gzip -h if you do not believe me)
and it will work properly. GNUzip (gzip) is still the best compression
program around. Sometimes better than LHA(RC). PKZip really is
outperformed this way.
------------------------------------------------------------------------------
Compactors
Time Crunch 5
Code Compressor
ECA Compactor
Speed-packer 1
From: aa...@cleveland.Freenet.Edu (Howard Herman)
Newsgroups: comp.sys.cbm
Subject: Re: Self-extracting archive creators
Date: 16 Aug 1995 08:25:40 GMT
John Iannetta, Sysop on the CBMAPP Forum on CompuServe, has authored the
SPYNE self-dissolving C64 file.
A SPYNE file component files can total up to 65535 blocks (about 16
megabytes). The maximum number of embedded files is 144, and there is
100% protection against duplication of filenames and insufficient room
on the destination disk.
A SPYNE file has the added advantage that it gives the user 2 options
to self-dissolve: (1) direct onto a 1541 formatted disk on which it
may currently reside (in other words it will make itself disappear from
a 1541 disk in order to make room for its parts), or (2) dissolve its
parts onto any Commodore disk drive, and retain its original SPYNE file.
SPYNE can dissolve files on RAMLink.
------------------------------------------------------------------------------
* 64copy
Newsgroups: comp.emulators.cbm
From: sche...@dcs1.uwaterloo.ca (Peter Schepers)
Subject: 64 Copy 2.08 released!
Date: Fri, 13 Oct 1995 17:14:57 GMT
Version 2.08 of 64COPY is now available for FTP download. Among the changes
from version 2.07 are:
* Major additions to the Hex editor such as:
1. Can now select (tag) an area for Copy/paste/zeroing (ALT-T)
2. Removed some annoying dialog boxes (when exiting, pasting)
3. Completed search engine.
* Added seven new configuration options, some of which are:
1. change sector interleave
2. Default line mode and color mode
3. Default T64 size
4. default Convert filetype
* Added support for creation/deletion of Directory separators ("--------")
* Added second bar graph for overall % of copies/deletes/converts/moves
and added bar graphs to most other functions.
* Added display of free blocks for D64, free entries for T64.
* Improved conversion of ZipCode/LNX/D64
* Altered (improved) sector interleave algorithm.
* *Many* bug fixes.
Thats most for now. Stay tuned for more features. Please read the
CHANGES.TXT file for more info and specific details on fixes or
enhancements, and don't forget to mail me with your thoughts on the
program. I enjoy any and all feedback.
It is available for anonymous FTP download from:
RUSH.UWATERLOO.CA (129.97.108.99), under G:\UTILS as the file 64CPYxxx.ZIP,
where xxx is the present version. Do a directory to see what version is
presently there. If anybody can upload it to other sites, please feel
free to do so. I don't have access to Frodo (its *way* to slow from
here), and I don't know of too many other sites that exist now. There are
also some stand-alone programs there (Zip2d64, d642zip, a C64 assembler,
etc) which might be of interest.
If you cannot access this site by FTP, email me and I will UUEncode it
and mail it to you. Please indicate if you must have it split into
smaller pieces (<64k chunks), or else you will get one large file, and
your mailer might not be able to handle this.
Don't forget to read the 64COPY.TXT file (not a really good manual, but
it does contain some helpful info), and please email me regarding your
feeling about this program, especially if you want an enhancement. I am
keeping a mailing list of all those who wish to be directly notified of
new version releases (just in case they miss the posting in
COMP.EMULATOR.CBM), so if you want your name on the list, let me know!
---------------------------------------------------------------------------
Synopsis:
64COPY is a conversion program designed to convert D64, T64. X64,
P00, LNX, ZipCode and Binary files between each other for the various
C64 emulators that are available. It also handles a variety of DOS
functions in a manner similar to Norton Commander. It is meant as a
companion program for Trans64, Star Commander, or any program which
converts 1541 disks to D64/T64 files.
Some of its more useful features are as follows:
* Full conversion between D64/X64/T64/P00
* Conversion between ZipCode/D64 and support for UnLynx only (No Lynx'ing)
* Full DOS directory manipulation/maintenance
* A powerful D64/X64 CheckDisk routine (it checks virtually everything
inside a D/X64 for integrity, errors) with result logging.
* D64/X64 hex/BAM sector editor (with copy/paste)
* Customizeable color scheme and many user-configurable options
* Uses only 24k when shelled out to DOS.
* It does a *lot* more, so try it out.
-----------------------------------------------------------------------------
Peter Schepers, |
Dept. of Computing Services, | The opinions expressed in the above
University of Waterloo, | rant are those of the poster, and not
Waterloo, Ontario, Canada. | necessarily shared by anybody else on
1-519-885-1211 ext 2456 | this planet (or employer).
From: sche...@dcs1.uwaterloo.ca (Peter Schepers)
Subject: 64copy 2.09 development
Date: Fri, 20 Oct 1995 12:56:18 GMT
As some of you know, 64COPY is in constant development, with 2.09
coming along. The only changes so far are with the HEX editor
(more streamlined) and the addition of a DISASSEMBLER (SHIFT F4)
Thats right, a disassembler. I was all fired up about writing this,
and finally started on it a week ago. I now have the basic engine
finished, and most of the assigned Fkeys work as well. Here is a brief
description of how it works.
1. Convert a file from D64/T64//whatever to BINARY. The disassembler
only works on DOS binary files, nothing else.
2. Set the program start address. This can be a little tricky, since
the file will contain as the first two bytes, the load address, so you
should set the actual address back 2 bytes from what you expect.
3. Start setting up .BYTE tables (the only kind allowed so far).
4. Set up the labels (for JMP's, JSR's branches, etc.
5. Once this is done (its actually a long and drawn out task), you can
dump it to a .ASM file to recompile. You can do this at any time, since
it is handy for checking the output, and looking for missed labels.
6. A job in progress is saved to a .OVV (OVerView) file. You can at any
time reenter a disassembly job by either selecting to disassemble the
fie you were working on, or select the .OVV file, and the proper file
will be called up for editing. I always look for an OVV file that goes
with the binary you are editing. If one exists, it will use it.
Thats about all there is. I don't know how useful it is, but it can
be either one of the best features I have, or completely useless. I don't
have the release version done (haven't even really begun to test it), but
if you want a pre-release, I can mail that out. Actually, what I will
do is leave a version on my machine just for testing. it will be called
64CPYB.ZIP (for Beta).
Keep in mind that the layout of the .OVV files is not near finalized,
so don't expect to be able to start a disassebmly job with this version,
and be able to keep working on it with the release version of 2.09. In
fact, I will *guarantee* it will not be the same ( I already have a few
additions in mind). Just use it for testing, no serious jobs.
The beta will hopefully be available by the end of today (Oct 20/95)
on RUSH.UWATERLOO.CA under G:/UTILS as 64CPYB.ZIP
If anyone has any comments, or suggestions for a better way to disassemble
files, let me know. This was about the best I could come up with (aside
from a better user interface).
Peter Schepers, |
Dept. of Computing Services, | The opinions expressed in the above
University of Waterloo, | rant are those of the poster, and not
Waterloo, Ontario, Canada. | necessarily shared by anybody else on
1-519-885-1211 ext 2456 | this planet (or employer).
------------------------------------------------------------------------------
12. TRANSFER
The CBM General FAQ from comp.sys.cbm discusses this topic widely on the
view from CBM machines.
12.1 CD-ROM
Instead of transferring your favourite games for the emulators, you may be
tempted finding most of them already cracked on many pirate sites and CD-ROMs,
though there might be a legal CD out there as well. (Not that pirating would
be legal, or encouraged by X64 -- it's just the existing situation.)
12.2 CBM
1) An Ibbem floppy drive simply
David> cannot read a Commodore disk, no matter what you do to it and
David> what software you use.
David> 1541 can read and write to IBM disks (using a program which
David> I've heard of but not tried called the Big Blue Reader).
That's partially correct: a 1541 can read and write MS-DOS disks, but
not with the commercial program Big Blue Reader, but with the PD
program 1541-dos written by Richard Hable and Daniel Fandrich.
Available at ftp.funet.fi:/pub/cbm/transfer/1541-dos/.
--
From: e902...@stud1.tuwien.ac.at (Stefan Froehlich)
Newsgroups: comp.emulators.cbm
Subject: Re: read 1541 floppys with a PC??
Date: 9 May 95 08:58:47 GMT
>>I 'd like to know if there is any way to read 1541 floppies with a 5 1/4 high
>>density floppy disk drive of a PC.
>>I have important documents in easyScript and my 1541 drive is broken, so what i
>>want is to read those disks with my PC and translate the information to a
>>standar file format.
But as the C128 can read foreign disc formats under CP/M which are
MFM-formatted, it is possible to read PC-floppies with the 1571.
I have done so, there is a special program available, which copies from GCR
disks directly to MFM disks. The program works with the C128 + 1571 and, too
with the C64 + 1571, if you modify your hardware a little bit.
Bye, Stefan
From: NEUS%mi...@magic.itg.ti.com
How do I get files from my PC to C64?
There are several ways. Probably the easiest if you have a 1571 or 1581 drive
is to use software that will allow you to read MS-DOS disks directly. Two very
good programs I'm aware of are Big Blue Reader and Little Red Reader. BBR is
much better, but LRR is PD and requires two drives. Take your pick...
If that fails, a program called x1541 will allow you to connect any serial CBM
floppy drive to an IBM through the parallel port. This also works well, but is
really slow (uses standard slow serial) and you need to build a special cable.
Finally, there is a null modem connection. This also needs some hardware, but
it should be easy to come by. You will need an RS-232 interface on the
Commodore, and a "null modem cable" which most computer stores should stock as
a standard item. NOTE--a regular RS-232 cable will not work. Connect the
cable between RS-232 ports on both computers and simply transfer files between
the two using a batch protocall (Y-Modem works well) with a standard telecom
package (I use Q-modem on IBM, Desterm on C128).
Mike Neus
NE...@timsg.csc.ti.com
From: lou...@symnet.net (Luis Hernandez)
Newsgroups: comp.sys.cbm
Subject: Re: How do I get files from my PC to C64?
1. modem or null modem
2. Big Blue Reader (commercial) or Little Red Reader (shareware)-1571 needed.
3. TRANS64_114, available at watson.mbb.sfu.ca /pub/c64/emulators
This option will also let you save whole-disk images to a 1541 from
d64 image files (for the emulators).
That's a few of many possibilities.
Use either Big Blue Reader available commercially or even better use
Little Red Reader which is free or shareware. I can't remember off hand
where it is available but ARCHIE should be able to tell you. The file
name is LRR200.sfx. You need at least 2 disk drives (1571 or 1581 to read
720KB disks).
Subject: Re: 1581 MSDOS ?
> I'm looking for a shareware program or utility that allows me to read MSDOS
> disks on my 1581 in 64 mode.
SOGWAP's Big Blue Reader exists in a 64 and 128 versions, and it will allow
you to read 720K disks on your 1581.
BBR can transfer programs between Amiga, PC, 64, and 128 (native and CP/M).
Little Red Reader.
It is PD and has no limit on the size of files that it will copy.
It requires a C128 and two disk drives. Can convert MAC text files as well.
From: Sy....@canada.tor250.org (Sy Ali)
Date: 14 Aug 95 03:40:12
Subject: Re: 1581 MSDOS ?
I happen to have an 8 block utility which will let you read, and copy
from a 720k IBM (in your 1581) onto a 1541 disk.
| Internet: Sy....@canada.tor250.org
From: paul....@ferrari.ct.se (Paul Fisher)
Subject: FDX000 MSDOS
Date: Wed, 23 Aug 95 21:24:00 +0200
Does anyone know WHY BBR 4.1 cant read normal MSDOS formated HD disks in
FD drives? What difference is there between the FD MS format and the IBM MS
format? (noticed that with F4 you can read the directory of both sorts) It
returns a HIGH CAPACITY disk error. Doesn't seem to have any thing to do with
size.. 1.44 is 1.44...
* Kermit
From: chrismc@news-server (Chris McCormack)
: One more thing, my kermit program takes alost 1 minute per 1K when
: downloading considering my equipment, barring getting a faster modem,
: or etc, what can i do to make it less painful
: current rate: download 48k in 35 minutes terrible!
Kermit is widely mis-understood, and receives a bad rap for speed.
With proper settings, it's actually pretty quick. The problem is the
default settings impose a nasty overhead by assuming things like a
7-bit link, need to quote a lot of special characters, etc. The other
drawback is the slow write speed of Commodore disk drives.
Depending on the terminal program you have, X-modem or Y-modem should
speed things up tremendously. Most unix versions of Z-modem also support
these protocals - usually under the names sb (for y-modem) and sx (for
x-modem). Use one of these and downloads should be snappier.
For a c128, both of these protocols are supported by DesTerm - a very
nice terminal program with snazzy options and robust Vt-100 emulation.
12.3 Amiga
From: v...@dutiws.twi.tudelft.nl (E.W.C. de Vos)
Subject: Re: Saving to D64FILES possible.
Date: Mon, 1 May 1995 11:38:35 GMT
I don't know if anyone is interested, but I just made a program which can save
to d64files, extract from them, and list the directory contents.
The program is for the Amiga.
Eelko
- Eelko de Vos v...@dutiws.twi.tudelft.nl
* Amiga Transfer Cable
The diagram for the Amiga to 1541 Cable (The Amiga equivalent to the X1541)
can be fount - at the moment - at URL:
http://stekt.oulu.fi:/~jopi/electronics/cbm/1541_to_Amiga.gif
Amiga parallel <-> C64
* PData (FTP: ftp.funet.fi, possibly aminet)
Transfers files between C64-amiga, but quite slowly...
>siirtaa tavarat Nepaan esim. PDataa kayttaen tai C64 emulaattorilla=20
>(Frodo) ja Amigaan liitetylla 1541 asemalla.
* (B)-Net by Mr.Sex
.d64 liikahtaa neban levylle n. minuutissa, zipcodet n. kahdessa..
* Over5 v0.463, by t...@stacken.kth.se
FTP: AmiNet in misc/emu/Over5_0.463.lha
for the C64/Amiga
It sets up a 32800 bps serial link between the amiga and the C64... then
you have programs for sending/receiving files/memory/diskblocks as
well as letting you use the amiga as a server for your C64...
--
* D64transfer
"C64transfer", which can be found at ftp.funet.fi.
It can only handle one file at a time, but it's really reliable (as opposed to Transnib).
However, I recently found an update to C64transfer, called D64transfer, which
can transfer whole D64 files directly to the C64 disk. It uses the original
C64transfer, except for an updated serverprogram on the c64 end, and can
be found at
pitel_lnx.ibk.fnt.hvu.nl /pub/c64/D64/D64trans.lha
The transferring is very slow, but it works reliably.
Finnish docs included. Could be in English by now.
* Jnet
BTW, If you build the cable for the program called Jnet (found on Aminet) you
can use that for Jnet, C64transfer and Transnib. I also have a version of the
Jnet program on the C64 end that's better than the original one (you don't
have to reload Jnet on the Amiga and transfer the server program to the C64
every time).
/Pelle
* Emul_1541
From: dd...@wumpus.cc.uow.edu.au (Pearse Daniel David)
Date: 5 Oct 1995 12:30:56 +1000
I just found a program on aminet under /misc/emu called emul_1541.lha that
is supposed to make the amiga behave as a c64 drive...
Dan
From: jh...@isosotka.cs.tut.fi (Salmij{rvi Janne)
Newsgroups: comp.sys.amiga.emulations,comp.sys.cbm
Subject: Emul1541, Does it work?
Date: 30 Oct 1995 11:54:13 GMT
NNTP-Posting-User: jhsa
Hi there...
Has anyone else been able to get this to work ? A small explanation...
Emul1541 is a program and a hardware interface for amiga that makes it
emulate 1541 drive. It connects amiga and c64 and amiga acts as a 1541.
It has been tested on several amigas and several c64s and it doesn't work
with any of them perfectly. With my amiga & c64 the transfer works okay
from c64 to amiga but not the other way (which is the much more important
direction). When trying to load stuff to c64 the programs just says
'COMMUNICATION BREAKDOWN' and c64 get File not found error. But as said
saving eg. a basic program from c64 works. Strange.
The hardware interface (contains one N7406) has been checked over and over
and it seems to have been built properly. Any help is much appreciated.
Thanks.
Janne Salmijärvi, jh...@cs.tut.fi
From: cou...@mail.bremen.pop.de (Count Zero)
Newsgroups: comp.sys.amiga.emulations,comp.sys.cbm
Subject: Re: Emul1541, Does it work?
Date: 30 Oct 1995 22:31:25 GMT
Salmij{rvi Janne (jh...@isosotka.cs.tut.fi) wrote:
: Hi there...
:
: Has anyone else been able to get this to work ? A small explanation...
: Emul1541 is a program and a hardware interface for amiga that makes it
: emulate 1541 drive. It connects amiga and c64 and amiga acts as a 1541.
: It has been tested on several amigas and several c64s and it doesn't work
: with any of them perfectly. With my amiga & c64 the transfer works okay
: from c64 to amiga but not the other way (which is the much more important
: direction). When trying to load stuff to c64 the programs just says
: 'COMMUNICATION BREAKDOWN' and c64 get File not found error. But as said
: saving eg. a basic program from c64 works. Strange.
:
: The hardware interface (contains one N7406) has been checked over and over
: and it seems to have been built properly. Any help is much appreciated.
: Thanks.
:
: Janne Salmijärvi, jh...@cs.tut.fi
:
A friend of mine got it to work by changing something on the schematics,
but when I tried it it still didn't work out for me either, although I got
schematics and U tell me whether it works that way or not ...
Count Zero/Talent
Newsgroups: comp.sys.amiga.emulations,comp.sys.cbm
From: s5...@csc.liv.ac.uk (P.J. Johnson)
Subject: Re: Emul1541, Does it work?
Date: Tue, 31 Oct 1995 19:28:50 GMT
In article <473jnt$g...@jupiter.NordWest.POP.DE>, cou...@mail.bremen.pop.de
(Count Zero) writes:
> Salmij{rvi Janne (jh...@isosotka.cs.tut.fi) wrote:
> : Hi there...
> :
> : Has anyone else been able to get this to work ? A small explanation...
> : Emul1541 is a program and a hardware interface for amiga that makes it
> : emulate 1541 drive. It connects amiga and c64 and amiga acts as a 1541.
> : It has been tested on several amigas and several c64s and it doesn't work
> : with any of them perfectly. With my amiga & c64 the transfer works okay
> : from c64 to amiga but not the other way (which is the much more important
> : direction). When trying to load stuff to c64 the programs just says
> : 'COMMUNICATION BREAKDOWN' and c64 get File not found error. But as said
> : saving eg. a basic program from c64 works. Strange.
> :
> : The hardware interface (contains one N7406) has been checked over and over
> : and it seems to have been built properly. Any help is much appreciated.
> : Thanks.
> :
> : Janne Salmijärvi, jh...@cs.tut.fi
> :
>
Emul_1541 is a bit flaky, in that if you reset or crash your c64 while it's
running, you'll invariably crash your migy too. Other than that, I've had no
problems LOADing stuff really. I keep an installed boot disk with Emul_1541 on
which it simply runs from its startup-sequence. This way, when the migy
(inevitably) crashes, you can be back up and running in seconds.(you can keep a
good selection of games on the disk too :-) )
Make sure you've pulled up all the i/o lines in the interface to 5v (open
collectors), and put in a decoupling cap ~0.1µFs between 5v and GND.
BTW: The Emul_1541 lead is similar to the A64/Frodo one, but is NOT the same.
Emul_1541 expects the 'ATN' line to be an INPUT, A64/Frodo need an output.
Have to go now and reload shotgun for next bloody 'trick or treat'ers.
Bye,
P.J.J.J.
* Parload
* Transnib
* Copy1581
* Run64
Run64 was something I got from a pal in Norway. 1451.lha is the name of Dan's
reader (was on Lennon or wherever I was fishing today
* Hardware Emulation
From: mda...@rainbow.rmii.com (Maxwell Daymon)
Subject: Re: possible to format disks c64 on other platforms?
> The Amiga's disk controller can read and write either MFM or GCR formats.
> It's a bit in a register that switches between these modes. The Amiga's DOS
> doesnt use GCR, but it doesnt mean you cant use it. :-)
: Note that 1581 disks already are MFM, not GCR.
Use <gasp> the Amiga 1020 drive. The companion to the Amiga 1010, the
1020 is a double-sided double-density 5.25" disk drive for the Amiga
computer. It was released with the Amiga 1000 just after 1985 with "Amiga
Transformer" a software PC-XT emulator.
Alternatively, you can simply plug an adaptor ($5) to a typical PC drive
into the Amiga 3.5" drive cable (which actually supports both types)
You can read, write, and format 1541, 1571, and 1581 disks with various
combinations of software such as Disk-2-Disk (1541/1571 with A1020 or
compatible), or "Read1581" (pretty obvious, eh?) and there are two others
faintly in my memory, but I'm having a hard time recalling the names.
--
+- Maxwell Daymon -+- mda...@rmii.com -+
From: "Edward C. Shaw" <eds...@iglou.com>
Subject: Re: READING AMIGA DISKS ON AN IBM
Date: Fri, 22 Sep 1995 18:51:25 GMT
There existed once a couple of files for early Amiga users to emulate
the 8088 computer. I think they were Cross-DOS and DOS2DOS. This must
be what you refer to when you say you are aware of going one direction,
but not the other. Otherwise, I am unaware of any AMIGA emulation
scheme for PC.
12.4 PC
12.4.1 What you'll need
: What do I use to convert games to and from .D64 format? I've got SF2 for
: PC but I'd like to play it on my regular C-64. Thanks.
You need your commie disk drive, a special cable, and trans64 (or one of the
other transfer programs).
Trans64 will tell you how to build the cable, or
if you buy one of the emulators (or at least C64S) it comes with one.
---
all you need for converting *.D64 back to c64 disk image
file is:
- a working 1541 etc. disk drive
- a cable that connects your PC's(?) printer port to 1541 etc. drive.
- a program that transfers the files back and forth PC and 1541
First you can download a file called X1541.ZIP, which you can find
from most of the c64 ftp-sites. It is a simple program that handles
the *.d64 files.
X1541 includes the instructions for building a cable used to transfer
*.D64 files.
: Well, the problem with transfering D64 files on a real C64 is that you
: need a drive that is bigger than a 1541, either a 1571 or 81 because the
: D64 files are about 680 block big.
With Trans64, Star Commander etc you can transfer a .d64 directly to the
disk, not as a file, but the disk becomes an exact replica of the .d64.
Using CBM printer
>The desired interface would then be a piece of
>hardware/software that takes the PC printer port output, processes it,
>then turns in into what the CBM printer expects to see.
A Plus-4 and an RS-232 interface and print it to the PC's com port instead
of the LPT port. I know of no interface that will do what you want. The only
PC to COMMODORE printer programs I know of all run as software (Device
drivers generally) in the PC.
12.4.2 PC Transfer Cable
The required cable is not difficult to make, even if you are unexperienced in
soldering. The pins are usually numbered on the connectors, so look carefully.
However, if it won't work, here are a few things to check out:
* Make sure all connections shown in the instructions are included.
* Test it with a multimeter to see there is no short circuit.
* Check (with C64) your drive is OK.
* Check the delay settings you're using on the program.
* If your PC is too fast, (e.g. a 486/66) it may not even recognize the disk
drive. All you'll need to do is to take the computer out of turbo.
* On some machines there is a setup/cmos procedure for making your parallel
port send and recieve insted of send only. Check your setup and see if it's
locked into send only.
I'm sorry to tell you that your parallel port seems to be one
of those who wouldn't run with the transfer programs. The only possibility
to get any of these programs work on your PC would be to by a second
parallel port and to try it with this port. I don't know if this will work
but it's the only thought I actually have :-(
--
>Could there be some minor difference between the old 1541 and the
>newer 1541 II that causes this problem?
the 1541, a 1541-II, and a 1581, and all of the external disk drives
work just fine.
X1541, Trans64/Star commander work fine with my 1541-II
From: i94...@redgum.bendigo.latrobe.edu.au (Loon)
one thing that had me stumped for a little while with x1541 was that the
parallel port at $378 is actually lpt2.
lpt1 refers to a port at $3bc which is the address used by those combo
mono display/printer cards.
From: co...@cs.utexas.edu (Corey Cooper)
Newsgroups: comp.emulators.cbm
Subject: x1541 cable stuff ...
Date: 6 Sep 1995 17:07:13 -0500
Finally got my x1541 cable. Now that it's here, it seems that almost
everything I ever had for my 64 is now available on one of the ftp
sites... almost.
Well, I have a few questions. First, I didn't read anywhere about WHEN
to connect my 1571 to my PC. Figured it didn't make much difference and
went by the old rule of turning the PC off, connecting peripherals, and
turning it back on. This FRIED my CMOS battery. I want everyone to see
this: THIS FRIED MY CMOS BATTERY. Had to set my CMOS settings several
times to get things back to normal and now I'm afraid to turn the thing off.
Be careful.
After restarting everthing, I turned the drive on and then connected to my
PC and everything seems to work fine. Trans64 transfers great but can't
seem to get Star Commander to recognize my drive. BTW, whomever the
author of that program is: it looks GREAT, very convenient. But it must
have taken me 30 minutes to figure out how to change the panels to access
my 1571. That is VERY WELL HIDDEN in the docs. Even then it said my 1571
wasn't connected ...
A while back I remember people discussing the problems of faster CPUs and
corruption when using Trans64 to copy disks. I remember several people
stating that taking the computer out of turbo mode seemed to solve the
problem. Can someone tell me what the final word on this is?
For me, copying a disk when the PC is in turbo mode had the effect of
Trans64 seeming to miss a few of the last sectors in the final tracks of
each section (that is, that last few sectors of the last track with 21
sectors, the last few sectors of the last track with 20 sectors, in
ascending order).
I found that if I took the computer out of turbo mode, began copying a
disk, let it proceed for about 6 to 8 tracks, and then put the PC back in
turbo mode, everything worked fine. I only have to do that for the first
disk, after that they all do fine in turbo mode.
Anyone else have insight into this?
-Corey
From: cka...@sdcc13.ucsd.edu (Po-Ching Lives!)
Newsgroups: comp.sys.cbm
Subject: Re: D64 images, and some questions
Date: 5 Sep 1995 15:08:59 GMT
>Ok, I have the program to convert a D64 to regular commie language, but
>it needs a 1541 and a 1571...Is there any way I can download a D64 to a
>1541, without the '71? I know a 1541 disk is too small for a 170K image,
>but there has to be some way to do it...And another thing, while Im on
>the subject, is there ANY version of PKUnzip 2.4 for the commie? I will
>pay money right now for that miracle...
You can, in answer to your first question, do the following:
download the image to a PC, use Trans64 or X1541 and a LPT-serial
cable, and use the PC to write the d64 to the disk. And you *could*
use a 1581 if you like. ;-)
In answer to your second question, there IS a pkzip compatible 64
unzipper, but really due to memory constraints it cannot be called
reliable. If you want it, though, I think it's on my CWI site
(ftp://ftp.armory.com/pub/user/spectre) or on Craig Bruce's
(ftp://ccnga.uwaterloo.ca/). IMO, though, you're better off with
Phil Katz's REAL version -- it's just plain faster too.
Toodles, Cameron Kaiser
cka...@ucsd.edu
visit the CWI home page: http://www.armory.com/~spectre/cwi.html
***
From: bkti...@aol.com (Bktiller) >>> Byron Tiller <<<
Subject: Re: Trans64 recognizes 1541, but C64S does not?
I had this problem as well. It ended up to be a setting on the parallel
card in the PC. Basically you need to set your port to bi-directional,
and PERHAPS not to any other setting like ECP/EPP . I added a cheap-o
second LPT port card and just cabled up to that, since the dox for my
expensive super-I/O card were mis-leading and/or wrong. Hope this
helps...
12.4.3 PC Transfer Programs
* x1541.exe
Old, actually the x1541.exe is the first C64 file copier for the PC.
Shareware. Not very fast; nowadays considered outdated and buggy. Has
companion prg CBMPR.EXE to drive CBM serial printers.
* Trans64
From: sch...@lila.informatik.uni-bonn.de (Bernhard Schwall)
Newsgroups: comp.emulators.cbm
Subject: ANNOUNCE: Trans64 1.21
Date: 5 Jul 1995 09:03:59 GMT
I've uploaded the new version of Trans64 (1.21) and the new version of the
lolevel transfer routines (2.2) to:
ftp.rz.uni-hildesheim.de
ftp.cs.uni-berlin.de
frodo.hiof.no
ccnga.uwaterloo.ca
ftp.giga.or.at
nic.funet.fi
ftp.seattlelab.com
Trans64 is a program to transfer files between the PC and a C64 floppydrive.
The floppy is connected with a simple cable to the parallelport of the PC.
You can transfer files among virtual disks, virtual tapes, dos and the
floppydrive. Also you can transfer whole disks if a 1541, 1570 or 1571 is
connected. The cable used for the connection is either the cable used by
X1541 or the cable used by Disk64E. The description of the cable can be
found in the online-help of Trans64.
Bernhard Schwall
From: TJ...@delphi.com
Newsgroups: comp.emulators.cbm
Subject: What do I use to convert games to .D64 format?
Date: 19 Jun 1995 02:32:39 GMT
> What do I use to convert games to and from .D64 format? I've got SF2
>for PC but I'd like to play it on a regular C-64.
Then get Trans-64, which supports fast disk access.
For instance, you can convert a whole .D64 image
over to a real 1541 disk in about 3 minutes using it.
FTP to lennon.engr.wisc.edu then /pub/c64/utils and look for
files with names like tr64-118.zip and x1541.doc
x1541.doc has instructions on how to build the x1541 cable.
Even if you don't intend to make the cable, Trans-64 is great
for organizing and manipulating .D64 and .T64 images.
Also, if you have access to two 1571 drives, and you have a 5-1/4 drive
on your PC, you can do it without the X1541 cable. Its a rather
elaborate process but if you want to go this route, email me.
Since you may need all the track and sector info in the .D64 file,
I don't recommend trying to transfer each file in the image via modem.
If you need help with any of this, let me know.
TJoe
> Is it at all possible to convert the emulator disk image files ".d64" onto a
>disk for use in a real commodore?
- Trans64 (TR64_118.ZIP), it takes about 7-9 minutes to transfer a whole
disk image with this program (X1541 takes about 9 minutes), but this
program can handle also *.T64 tape images. (I don't know if this
program doesn't like my PC, but there occurred lockups frequently and
I had to cold-boot my computer.)
> Trans64 (tr64_114.zip). It can copy between disks and tapes, too.
****
kasittaakseni .P00 tiedostot siirtyvat myos.
* Disk64e
Subject: Re: Which cable is better? x1541 or Trans64?
You mean the X1541 and the Disk64E cable, don't you? Disk64E, the predecessor
of Trans64 (written by the father of the author of Trans64) used ONLY the
Disk64E cable, but Trans64 uses both of them. The X1541 seems to have become a
standard as the other transfer utilities (e.g. The Star Commander, written by
me ;-) ) and the emulators use it, as well (I'm sure about C64S, does PC64 also
use the X1541 cable?). Although the cables are differnet only in their pinouts
(and not their usage) I think the X1541 cable would be a better choice. Good
luck!
Joe Forster/STA
s...@ludens.elte.hu
* Star Commander
- Star Commander (SC_BETA5A.ZIP). This is fastest I've seen. In fastest
mode it can transfer a whole disk image at 2 and half minutes (!).
This one I prefer the most. I'm not sure if it can handle *.T64 files,
but in speed it's superior with *.D64 files. (This worked perfectly
without any lockups in my machine)
Olmi
--
From: u941...@muss.cis.McMaster.CA (T.A.Rahim)
Newsgroups: comp.sys.cbm
Date: 7 Jun 1995 17:02:49 -0400
Well I do have a program for the PC (XFERPC(??) that simply has a little
file from $0334-$0400 (c64) that recieves a file from the PC by typing
"x64.exe filename". The only problem is I don't have a PC. I know there
is one like that for the amiga but I forgot who had it!
P.s.: How does prlink work?!
* Emulators
** PC64
>> So, can you port files back to the C64 with the PC64 (which I'd
>> prefer to use) easily?
the built-in transfer in PC64 works in both directions. PC to C64 is 2:30
min and C64 to PC is 1:40 min per disk image. And it's safe.
But it works only in the registered version.
** Com1541 (C64S)
From: c94p...@ida.liu.se (Per Einarsson)
>: Can anyone tell me of a utility to convert a .d64 disk
>: image into an actuall C64 disk [using the x cable].. In
>: other words, the reverse of com1541 that comes with C64S..
>: I don't want to write files but actual disk images.. Thanks
/Pelle
******************************************************************************
12.5 CBM Networking
From: r...@dce.vic.gov.au (Russell Alphey)
Newsgroups: comp.sys.cbm
Subject: Re: Files from Pc - C64
Date: 7 Jun 1995 09:39:26 +1000
> 64NET tranfers files from PC
> (or AMIGA) to c64 through the parallel or serial port ?
****
From: piir...@mopo.cc.lut.fi (Antti Piirainen)
Subject: Re: c64 - PC kytkenta
PC-levyj{ (kova & korput) saadaan k{ytetty{ 64Net-nimisen ohjelmiston
kanssa, kaapeli k{ytt{{ mm. 64:n user porttia. Rekister|inti on
ohjelman k{ytt{miseksi l{hinn{ pakkotoimenpide, hinta noin 50-60 USD
64NET v1.80 features...these supersede features mentioned further on.
This shareware version allows all features of the registered version except
saving from the 64 to the PC.
New features: Track and sector support on 64NET drives, transparent handling
of various archive types, including .D64, CBM zipcode (1!...), .zip, .arj,
etc.. GEOS is supported, but requires an add-on driver not supplied in this
bundle. Negotiations are underway with the German author of the GEOS patch to
determine how it can be distributed.
*** 128 mode support is now a reality!!! ***
64NET v1.65 features:
Some quick points about 64NET:
* 64NET is a network redirector system which allows a C64 (or C128/C65 in
C64 emulation modes) to access the logical drives of a PC.
* 64NET is _NOT_ a BBS networking programme! (However work on a "dial-up"
extension to the system is under consideration).
* 64NET requires ABSOLUTELY NO DISK PARTITIONING or other nasty things
like that to mount the C64 filesystem. All files are stored as normal PC-DOS
files, and there are NO INDEX FILES, ie you can copy, delete, rename the
files stored as you like. However it is recommended that you maintain the .N64
extension.
* Upto 256 partitions can be allocated, with partition numbers ranging from
1 to 32767, including direct links to subdirectories. Partitions can also
be names, eg. "DH0".
* LOAD, SAVE, OPEN, CLOSE, GET#/GETIN/CHRIN, PRINT#/CHROUT are all
supported at the assembly code level.
So what does this DEMO version do and not do?
* SAVE will have no real effect, although it will appear to.
* OPEN will only work to read from files, with the exception of the
command channel which can be written to.
* All networking facilities (user id's, logons etc) are intact.
* BURST LOADING is 100% in (with a C128 loading 200 blocks takes approx 3
seconds! - ie upto 20KB/second)
* All the other frilly bits and pieces are in.
OK, so what do i need apart from this archive??
The 64NET interface cable
This cable connects from the user port of the C64/C128/C65 to a printer port
on your IBM compatible. The required pinouts are below:
USER Port PC Printer Port
------------------------------
A (GND) 25 (GND)
C (pb0) 10 (an input line)
D (pb1) 11 (an input line)
E (pb2) 12 (an input line)
F (pb3) 5 (db3)
H (pb4) 6 (db4)
J (pb5) 7 (db5)
K (pb6) 8 (db6)
L (pb7) 9 (db7)
There are no components involved, just connect the appropriate pins and your
set!
Transfer any C64 files to the IBM by any means and LOAD them using 64NET.
They can also be converted to native .N64 format using the CVTN64
programme to allow 16 character file names.
LOAD any of the programmes from the EXAMPLES directory.
NOTE: To move into a subdirectory you can simply LOAD the directory name,
or for those already familiar with subdirectories on C64 devices
you may use the CD or CP disk commands.
NOTE: Any action which actually requires writing to the PC's drives will
not function in the DEMO version. This may include using OPEN to read a
directory under certain circumstance.
If you really like the 64NET system, and would like to purchase the commercial
version, please contact the closest 64NET dealer to you:
Europe: Michael Renz
+49 2227 3221
Australia: Russell Alphey
+61 3 427 8558 (A/H)
North America:
Peter Fiset
Anywhere else: Choose the nearest!
--
From: gard...@ist.flinders.edu.au (Paul M. Gardner-Stephen)
Newsgroups: comp.sys.cbm
Subject: 64NET/2 aka 64NET/TCP aka NET-8
Date: 16 Jun 1995 01:09:27 GMT
Hi all!
Just a brief word on the front of the new version of 64NET which is almost
at the "RSN" stage.
The new version offers:
* Near 100% compatibility with all non fast-loading software
* Replacement kernel option
* Direct access to FTP and WWW through the ftp: and http: special paritions
* Divert upto 32 devices to the network
* *Real* printer diversion
* Improved file system
* New DOS which is near 100% compatible to CMD's HD-DOS(tm) to aid software
compatibility.
* Ability to work over a modem and the internet! IE - if a site runs a
64NET/2 daemon you can have direct access to FTP as though it were a nice
hard-disk on your desk (if a little lagged).
* 1541,1571,1581 Emulation partitions
* Various connection options (Swiftlink, bi-directional Parallel etc)
NOTE: The above details are subject to change, and are offered only as a
indication of the intentions of the software writers of 64NET.
Paul Gardner-Stephen,
--
+-------------------------------------------------------------------------+
|Paul Gardner-Stephen USENET: gard...@ist.flinders.edu.au |
| BBS: Fishbowl +61 8 2771361 v.42, 14k4 |
| 64NET Author Voice: +61 8 2777479 +9:30 GMT |
| C64 Coder Snail: 1 Hurst St,Morphettville SA 5043 |
| Highlander/FairLight Australia. |
| IRC-Nick: Highlandr |
| 3:633/272.2 Html: down :( |
+-------------------------------------------------------------------------+
-------------------------------------------------------------------------------
13. FURTHER READING
13.1 X64 Documents
The following documents come with X64:
x64.{man,cat} X64 manpage
petcat.{man,cat} petcat manpage
recomment.man recomment manpage
README X64 installation guide
README.RUN x64run front-end
Emulation Details on X64 and different file formats
DIN_charset DIN and ASCII charsets for serial printers
Star.codes Printer control code list
cbm_basic_tokens BASIC token code list
pal.timing VIC-II timing revealed
64doc Extensive CPU documentation
PETdoc Some notes on the PET series
13.2 Other Documents
The files listed below are available via FTP on x2ftp.oulu.fi:/pub/cbm/
and ftp.funet.fi:/pub/cbm/ if not stated otherwise.
Video Timing
pal.timing
Memory
All memory maps are at:
x2ftp.oulu.fi:/pub/cbm/maps/
and ftp.funet.fi:/pub/cbm/maps/
c128-basic.diffs
c128-kernel.diffs
c64-kernel.diffs
vic20-kernel.diffs
c64.pla.equations
c64.pla.functions
32K Internal VIC-20 Memory expansion are located at
ftp://x2ftp.oulu.fi:/pub/cbm/docs/VIC-32K-expansion
Internal C64/C128 Memory expansions
The comp.sys.cbm General FAQ
ftp://ftp.funet.fi:/pub/cbm/documents/1028/
ftp://ftp.funet.fi:/pub/cbm/documents/256kB/
Disk Drives
Full 1541 manual ftp.funet.f:/pub/cbm/documents/oc-118.manual
1541.tricks
Printer
DIN_charset
Star.codes
Miscellaneous
cbm_basic_tokens
csg.chips.info
hidden_secrets
13.3 FAQs
For full collection of FAQs, visit rtfm.mit.edu or the nearest of its
mirrors (e.g. ftp.sunet.se)
comp.sys.cbm Commodore FTP Sites List
comp.sys.cbm General FAQ
comp.emulators.cbm FAQ
comp.emulators.misc FAQ
PC File formats FAQs
x2ftp.oulu.fi:/pub/msdos/programming/formats/
(American) Copyright FAQ
RTFM has reorganized some of its FTP directories, specifically the
law-related ones. The following URLs will point to the current version
of the Copyright FAQ:
ftp://ftp.netcom.com/pub/ca/carrollt/law/copyright/faq
ftp://ftp.aimnet.com/pub/users/carroll/law/copyright/faq
ftp://rtfm.mit.edu/pub/usenet/news.answers/law/copyright/faq
13.4 Internet Resources
X64 Emulator / Simulator For Unix
http://stekt.oulu.fi/~jopi/x64.html
SID Emulation
http://stud1.tuwien.ac.at/~e9426444/index.html
Programming languages
http://www.wimsey.com/~danf/cbm/languages.html
6502 Cross-Development Languages and Tools
http://www.wimsey.com/~danf/cbm/cross-development.html
The Commodore 64 WWW Server.
(Has a few c64s and x64 documents)
http://www.hut.fi/~msmakela/c64.html
Commodore 64 computing (Home of the comp.sys.cbm FAQ)
http://www.msen.com/~brain/
WWW Personal Computing and Emulation Homepage
http://www.cs.umd.edu/users/fms/comp/
Commodore emulation
http://www.cs.umd.edu/users/fms/comp/Emulation/Commodore.html
Small Systems Home Page
http://www.sys.uea.ac.uk/~u9428232/small/
USENET FAQs (from rtfm.mit.edu)
http://www.cis.ohio-state.edu/hypertext/faq/usenet/FAQ-List.html
13.5 Commodore Manuals
Commodore VIC=20 Programmers' Reference Manual
Commodore 64 Programmers' Reference Manual
Commodore 128 Programmers' Reference Manual