So I've been playing around, going through the tutorials in the
users guide so I can learn BASIC. But its really a hassle to type
in every program. I run linux, so the only way I can see to avoid
typing it in is to cut'n'paste to a text file, plug my 1541 drive
into my PC, copy the program to a floppy (using cbm4linux), then
edit that file from a C-64 or an emulator to fix any character
conversion problems.
Are there any emulators which allow me to paste text directly
into them? Also, are there any emulators that will work directly
with files, not just disk/tape images?
thanks,
Jim
There's a program called PETCAT that can tokenize a text file into a C64
BASIC program file. I think it comes with VICE.
--
White Flame (aka David Holz)
http://www.white-flame.com/
(spamblock in effect)
Have you considered writing in C? CC65 (http://www.cc65.org/) is a cross
compiler that runs on your PC.
> Are there any emulators which allow me to paste text directly
> into them?
None that I'm aware of. There's a tool to convert ASCII text to
tokenized BASIC programs, though. Maybe someone could provide a link?
> Also, are there any emulators that will work directly
> with files, not just disk/tape images?
VICE does: under Windows, turn off true drive emulation, and go to
Settings/Device Settings/Drive 8 (or 9), then select Directory and
choose one. You may have to read the docs to find out how to do that
under Linux.
Regards,
Michael
--
From-address is valid, but used as spam trap. Use the reply-to address,
substituting the current year and month if necessary.
> dogshu wrote:
>>
>> I'm interested in learning how to program my C-64. I have a CS
>> degree, and I have worked with assembly before (MIPS assembly,
>> but still its assembly), so learning 6502/6510 isn't too
>> daunting. But I don't want to be writing 100 line assembly
>> programs when I could be writing 10 line BASIC programs.
>
> Have you considered writing in C? CC65 (http://www.cc65.org/) is a cross
> compiler that runs on your PC.
Yes, C is my favorite programming language. I actually don't
expect to develop anything useful.. I've never programmed in BASIC
before and I'd like to see what I can do with it. I'm considering
developing for the C-One, and I think I should have at least a
little background in C-64 programming.
I do plan on using cc65 after I learn the basics of BASIC...
but I don't think I'm going to be doing alot of C development on
my C-64, I'm too used to "infinite" amounts of memory (like the
C-One will have).
>
>> Are there any emulators which allow me to paste text directly
>> into them?
>
> None that I'm aware of. There's a tool to convert ASCII text to
> tokenized BASIC programs, though. Maybe someone could provide a link?
>
>> Also, are there any emulators that will work directly
>> with files, not just disk/tape images?
>
> VICE does: under Windows, turn off true drive emulation, and go to
> Settings/Device Settings/Drive 8 (or 9), then select Directory and
> choose one. You may have to read the docs to find out how to do that
> under Linux.
>
Thanks! Under linux, its Settings->Peripheral Settings->Device 8...
However, when I try to load the files, it seems to freeze up the
emulation... It prints out "Loading" and "Ready.", but doesn't give
me a cursor and won't let me type anything in unless I reset it.
The same thing happens even after I process the file with "petcat".
I'm using VICE 1.11.
Anyway, its late, I'll come back to it again in the morning.
thanks,
Jim
d> However, when I try to load the files, it seems to freeze up the
d> emulation... It prints out "Loading" and "Ready.", but doesn't give
d> me a cursor and won't let me type anything in unless I reset it.
That's what the C64 basic does if you load something that isn't a
valid basic program.
--
___ . . . . . + . . o
_|___|_ + . + . + . Per Olofsson, arkadspelare
o-o . . . o + Mage...@cling.gu.se
- + + . http://www.cling.gu.se/~cl3polof/
>>>>>> "d" == dogshu <dog...@sdf.lonestar.org> writes:
>
> d> However, when I try to load the files, it seems to freeze up the
> d> emulation... It prints out "Loading" and "Ready.", but doesn't give
> d> me a cursor and won't let me type anything in unless I reset it.
>
> That's what the C64 basic does if you load something that isn't a
> valid basic program.
Ahhh I see. Also I figured out that I am using "petcat" incorrectly.
I think I'm close to getting this working. I run
"petcat -w -2 -o JIMSPRG.P00 jimsprg.txt"
And it seems to create a basic program.
But when I list the directory from VICE, it shows nothing but
special characters for the filename. This happens whether the
filename is uppercase or lowercase.
Also, when I petcat the converted file (when I run
"petcat JIMSPRG.P00"), it shows a bunch of weird instructions:
10 hex$valrlcr peekjoyelse($cec3)right$($cec7) peekatnrgrrgr
20 rdothex$right$($ced4) ""
25 ascjoyhex$ tron=1 to 10: rdothex$right$($ced4) "": ($cec5)troninstr
30 ascjoyhex$ peekrgr=1 to 40
The line numbers are right, but that's not what is in the file.
It seems like I am converting the file incorrectly. Anybody know
what I'm doing wrong?
thanks,
Jim
I am generally doing it the brute-force way. I create a .d64 image. Then
save my files in the .d64. I am simply writing the programs in the VICE 1.10
emulator. I am simply making some test apps. That are meant simply to test
out ideas. I am looking for a good Assembler written to run on a c64 that
can be DLed to a PC and ran under c64 emulation via VICE. Meanwhile the test
file for now is simply in BASIC. Later, I will get the XE1541 adapter.
I really perfer programming on the platform in which I am creating the
program for.
d> I think I'm close to getting this working. I run
d> "petcat -w -2 -o JIMSPRG.P00 jimsprg.txt"
d> And it seems to create a basic program.
d> But when I list the directory from VICE, it shows nothing but
d> special characters for the filename. This happens whether the
d> filename is uppercase or lowercase.
petcat doesn't generate a .p00 file, it generates a raw C64 binary,
which usually has the suffix .prg, if any at all. Also, the syntax for
the w flag is -w2 and the -2 flag is only for when detokenizing.
petcat -w2 -o jimsprg.prg jimsprg.txt
should do the trick.
Michael J. Schuelke <MJSch...@hotmail.com> writes:
>>Are there any emulators which allow me to paste text directly
>>into them?
>None that I'm aware of.
Power64 for the Macintosh will. It's a very handy feature.
--
Cameron Kaiser * cka...@stockholm.ptloma.edu * posting with a Commodore 128
personal page: http://www.armory.com/%7Espectre/
** Computer Workshops: games, productivity software and more for C64/128! **
** http://www.armory.com/%7Espectre/cwi/ **
Jim> Are there any emulators which allow me to paste text directly
Jim> into them?
The X11 version of CCS64 1.09 that I created in 1997. Also, the
Windows version of Yape should allow copying text from the screen to
the clipboard.
Marko
>>>>>> "d" == dogshu <dog...@sdf.lonestar.org> writes:
>
> d> I think I'm close to getting this working. I run
> d> "petcat -w -2 -o JIMSPRG.P00 jimsprg.txt"
> d> And it seems to create a basic program.
>
> d> But when I list the directory from VICE, it shows nothing but
> d> special characters for the filename. This happens whether the
> d> filename is uppercase or lowercase.
>
> petcat doesn't generate a .p00 file, it generates a raw C64 binary,
> which usually has the suffix .prg, if any at all. Also, the syntax for
> the w flag is -w2 and the -2 flag is only for when detokenizing.
>
> petcat -w2 -o jimsprg.prg jimsprg.txt
>
> should do the trick.
Thanks! Works perfectly. Also, the reason I was getting weird
instructions output from petcat was that the file was all
uppercase. After I converted it to lowercase petcat was able to
convert it properly.
thanks,
Jim
Thanks, that is definately useful. So you know, new
distributions use gcc 3.2, which is incompatible with
C++ binaries compiled from earlier gcc versions. You
may want to consider distributing linux binaries.
I'm considering using ccs64 as my main "play around
with code" platform, but I'm having trouble figuring
out how to configure it. I tried putting this line
in /etc/X11/Xresources:
ccs64.speed: 50
but it doesn't seem to work. What is the correct way
to write that line?
thanks,
Jim