| |
Darkus
Registered: Apr 2007
Posts: 8 |
Coding for beginners
I`ve been searching the net for assembler guides and applications but I hoping someone can recommend the best guides and programs I should use for starting out - plus are there any issues with using emulators only ? Anyone who may answer these questions, please bare in mind I know very little about the C64 platform at this stage :) |
|
... 122 posts hidden. Click here to view all posts....
|
| |
Martin Piper
Registered: Nov 2007
Posts: 722 |
I find ACME suits my needs, especially after a couple of tweaks to allow it to output warnings in Microsoft Visual Studio format. This lets me build in the IDE and press F4 to jump to reported warnings/errors. I've found using a nice modern IDE with source control really helps improve the C64 coding experience. :)
I also quite like debugging in VICE and altered ACME to output labels in VICE debugger format. When the PRG loads just load the labels in the debugger and then the disassembly is much easier to read. I did think about tweaking VICE to automatically load labels if it detected the file existed when loading a PRG with the same file name, but never got around to it. An alternative would be to write a debugger hook back to Visual Studio to enable me to do breakpoints and source single stepping, but that is also a much larger project. ;)
I've uploaded the tweaked ACME sources and a build here. http://codebase64.org/doku.php?id=base:tool_sources#sources_for..
|
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
These advices are all very good, but don't forget the most important thing - eat/drink lots of caffeinated stuff, otherwise you'll never have the drive you need to try, try and try again thousands of times over until you figure out how to do something decent.
|
| |
HCL
Registered: Feb 2003
Posts: 728 |
Fir5t you n33d 7o 134rn t0 5pe4k 1ike teh 1337 ha**0r5, otherwise you'll never be able to learn coding, no chance. Practice here in teh shit ph0rumz a few light-years, and then come back and learn coding.
And then when you become famous, remember who gave you all this good advice!! |
| |
Burglar
Registered: Dec 2004
Posts: 1101 |
Quote: These advices are all very good, but don't forget the most important thing - eat/drink lots of caffeinated stuff, otherwise you'll never have the drive you need to try, try and try again thousands of times over until you figure out how to do something decent.
dont forget weed! it'll give you really creative coding solutions that miraculously stop working the next day ;) |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
Quote:dont forget weed!
I wouldn't know about that, but alcohol in the right dose can be a help too...
|
| |
plagueis
Account closed
Registered: Dec 2007
Posts: 48 |
Hello all beginning 6510/6502 coders.
I had a c64 in the 80's and now recently purchased one again off of ebay. I always wanted to learn to code, back then, but I was younger and my attention span was never really there, plus, living in a small town I didn't have any local machine code mentors.
Now, after reading Puterman's excellent tutorial and many disk mags (such as Coder's World 1,2 and 3...and all the Attitudes), I have mastered quite a bit of the basics, and even have managed to create a one screen intro. I started about 3-4 months ago, using primarily the CCS64 emulator, and also Vice. I've mostly been using Turbo Illasm off of the "Coder's Orgasm V3" disk. I've also written quite a few routines (timed and $d011 raster bars, etc) using the monitor in Final Cartridge III, and Action Replay VI. I have those ROMs, plus I also have the hardware for Final Cartridge III. The only problem is, I haven't had the chance to test any of my code on the real hardware due to lack of a monitor (screen). I hope to remedy that soon.
So mainly I just made this post to share my experiences with other beginners. Cruser was absolutely correct about needing Caffeine to stay focused on figuring out new routines and effects, and stay on it until you get them working the way you want. I have made a lot of progress in only a few months after starting from scratch, but I have a long way to go.
So, Turbo Assembler for sure, only after a decent knowledge of coding in the monitor.
Action Replay VI or Final Cart. III
Read anything by Puterman (great tutorials...plus he doesn't always give you *all* the answers)
Read all 3 issues of Coder's World, then read them again.
Read Attitude 4,5,etc... |
| |
Radiant
Registered: Sep 2004
Posts: 639 |
Quote: vice monitor is ok for debugging, but for coding? nah.. Maybe TMR would like it :)
Coding in any monitor these days is masochism. The VICE monitor is excellent because it's such a fantastic gateway between the emulated C64 and the host machine. |
| |
assiduous
Account closed
Registered: Jun 2007
Posts: 343 |
Quote:Hoxs is much slower (the price you pay for better emulation) but it will emulate almost anything you throw at it.
And if it won't,report it to the author, he fixes anything you throw at him within a few days.
although hoxs64 is deadly accurate (ccs64 and vice are nothing close) i wouldn't trust it in all circumstances. if vice, ccs and hoxs display differently it's always a good idea to check on a real C64. In the great majority of cases Hoxs64 will prove to be accurate but not always. A few days ago I found a minor VIC bug affecting Hoxs64 and CCS64 and not present in VICE and it is now being fixed for the next release of Hoxs64. |
| |
HCL
Registered: Feb 2003
Posts: 728 |
You read Puterman's tutorial!? Oups, we're about to see some rather weird stuff here soon ;). |
| |
The Shadow
Registered: Oct 2007
Posts: 304 |
Recently I bought a 64 from eBay myself. Doodling around on an emulator is fine. When it concerns the hardcore details, an actual 64 is a must. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 - Next |
