I noticed not much has been happening with the Type-Ins from Amstrad Action since I submitted the Type-Ins for AA17, which was back in 2008. Anyway I've been doing the Type-Ins from AA16, unfortunately I thought I had them all done, when I discovered there was 5 pages of Type-Ins from that Issue (as opposed to the 2 I had done).
I've completed:
- Fast Basic double-height
- Calendar and
- Snowstorm
Unfortunately it wasn't easy typing those programs in (I'm working on the AA Scans from the CPC Oxygen website), and had to debug Fast Basic double-height because the print AA used for those programs during that period is terrible! ??? Fortunately the Double-Height Character generator from AA17 solve what I had wrong. I've got the Calendar working really good for the screen, on the printer though I'm not sure if it's a fault from the program or if it's the Emulator talking to the Printer which isn't aligning up the text properly. The program itself uses the same routine for the screen printing as well as the printer (by assigning a variable alongside the print which represents the value for the screen or printer), I'm using Winape. This issue of AA also features another printing utility with Shady Dump. Can someone let me know how accurate the Winape Print is please?
Other programs from this issue include:
- Artist
- Wandering through space
- Pyramid
- Shady Dump
- Screen squash
Might do the Artist next since appears to be the biggest of those programs! I'll attach what I've currently done from AA16. And on the Disk Image I've also included the opening Introductions which AA made for those programs.
Quote from: CP/M User on 10:22, 03 October 10
Unfortunately it wasn't easy typing those programs in (I'm working on the AA Scans from the CPC Oxygen website), and had to debug Fast Basic double-height because the print AA used for those programs during that period is terrible! ???
I agree. I used to type in all capitals because I couldn't always tell if it was a 1 or I, O or 0, or even 8 and B in places. No wonder I had such a hard time debugging.
Is there a particular issue or two you want typed up? I'm up for a bash :)
betpet wrote:
I agree. I used to type in all capitals because I couldn't always tell if it was a 1 or I, O or 0, or even 8 and B in places. No wonder I had such a hard time debugging.
Is there a particular issue or two you want typed up? I'm up for a bash :)
Well this webpage (http://www.cpcwiki.eu/index.php/AA_Type_Ins) shows what's missing - Typeins from Issue 5-15 aren't currently being worked on. I'm working on Typeins from Issue 16. At the moment that webpage is only up to Issue 24, so anything between Issue 18 and 24 isn't being worked on.
I've got most of the programs from Issue 16 working, but now I've got this horrible Machine Code program which I cannot seem to find the bug. I think the problem is like what you said - "B" could be an "8", machine code data lines don't use "l" or "i" because their Hexadeciminal opcodes ("0-9" and "A" to "F"), though it's annoying because I was one digit off the correct checksum code and haven't been able to track it down! >:( I've disassembled the program and found one error with it, though haven't been able to track down what the others could be (because it still doesn't add up properly with the checksums!). Even more annoying because it doesn't tell you which line the fault is.
What I found to be easier was to type in the program in Winape, and have the Type in onscreen and blowup the picture which makes it a bit easier to read and work out what's what, but beware the typeins with machine code routines in them cause you'll be pulling your hair out!
I know what you mean. I've been typoing in Machine code apps from Computing with the Amstrad recently in an attempt to learn Z80 coding. It brought back memories of my struggles with the font in the magazines. I'll have a look next week and knock a few in. :)
Will you be uploading these to the wiki?
Gryzor wrote:
Will you be uploading these to the wiki?
That's the general plan! ;D I'm just having so much trouble getting the last one correct from AA16 that it's a nuisance! :( Of course there's quite a few Screen Squashers available for the CPC and this is another one to add to that list, though I just felt excluding Typeins isn't good practice (even though I never used to type in every listing from each issue).
Ok, I need a link to the scans for those type-ins before I can type any in! :)
Their on CPC Oxygen Webasite - link here (http://cpcoxygen.fxwebdevelopment.com/aa.html).
You'll need to click the issue you want, and then the Contents page can be used to skip to the Type Ins scan.
Quote from: CP/M User on 08:54, 12 October 10
Their on CPC Oxygen Webasite - link here (http://cpcoxygen.fxwebdevelopment.com/aa.html).
You'll need to click the issue you want, and then the Contents page can be used to skip to the Type Ins scan.
Excellent! I'll get typing when I get 5 minute to myself :)
I have typed in several programs during the past few years - always quite rewarding... :)
Gryzor wrote:
I have typed in several programs during the past few years - always quite rewarding... :)
I dare say that won't include the Screen Squash program from AA16. If you want to learn all about Checksums, Disassemblers & Love a challenging Typein to code in, I can definitely recommend that one! ;)
What would be your favourite Typein of all time?
I collected a whole heap of Amstrad Actions - from AA44 til when the magazine closed it's doors, though because Australia were months behind the UK, the last Issue for me was 115, but I think it was the Issue with Fantasy World Dizzy on the Covertape which had the last lot of Typeins (Issue 108?). I remember David Hall having a whopping Space Storm 3 in one of those last issues and the Halloween which was with it was quite good too. Someone also did a BASIC platform game in the following issue I think - which was also quite good, nothing fancy, though just good clean fun. Games I perhaps had the most fun with, AA had the good one here and there. Didn't really know much until I brought a CPC6128 which came with a heap of Computing with the Amstrad Mags. Those programs blew your normal stuff again, probably the inspiration for people like David Hall & Sean McManus to come out and produce some nice looking programs! ;D
Quote from: CP/M User on 09:08, 11 October 10That's the general plan! ;D I'm just having so much trouble getting the last one correct from AA16 that it's a nuisance! :( Of course there's quite a few Screen Squashers available for the CPC and this is another one to add to that list, though I just felt excluding Typeins isn't good practice (even though I never used to type in every listing from each issue).
I have been typing a few listings from issues 5-7 of
Amstrad Action and I am currently working on issue 8. However, I think the formatting of the AA Type Ins (http://cpcwiki.eu/index.php/AA_Type_Ins) entry needs to be improved, and I also have some other questions and suggestions:
- Should the current screenshot images be replaced with a gallery-style table, as used in some entries for commercial games (see the entry for Orion Prime (http://www.cpcwiki.eu/index.php/Orion_Prime) for an example)? The current screenshots are too large and I am unable to scroll the page to the right using Firefox!
- Should the instructions for each type-in be bundled with the DSK image, or is it preferable for them to be downloaded separately? (The instructions would be too long to include in the main AA Type Ins entry; we would have to split the page and create new entries for each issue.)
- Do we continue to name the ZIP files as AA_0xx_-_Listings.zip? I prefer something like AA0xx_Type-Ins.zip. Is it possible to rename files once they are uploaded to the wiki?
I agree about the screenshots (given I uploaded the Screenshots for the AA17 Type-ins), though I feel they should be completely removed. The Orion Prime entry is a nice example, though I'm also concerned about how much editing was involved to get it looking like that and given that the entry for the Type-ins page would be subjected to future updates, the easiest approach seems like the best approach. Personally I prefer the approach I made on my Turbo Pascal Website, I did have to go to a bit of trouble initially to setup tables as such, but once their in place, adding additional stuff to the site isn't a problem.
I like the idea of the instructions being on the Disk Image, I only wish I knew how I could get Protext to save straight out ASCII rather than Formatting it's own Gibberish on top of it, because of that I've been using the Turbo Pascal editor! ;) Once it's on a Disc the Instructions can be Printed or Displayed, I have a simple ASCII viewer program somewhere (not sure if it can dump to printer, though with some simple modifications it can cater for both).
Not sure how renaming the files works, from memory I think I had to do just that, or perhaps it's a question of Deleting the Old File from the Wiki, renaming it on your computer and uploading it again.
I personally like the screenshots on the wiki type-ins pages as I can quickly have a look and see from them which ones I remember.
I doubt I would trawl through loads of DSKs and run each one to see if I know it.
Quote from: CP/M User on 01:29, 19 October 10
I agree about the screenshots (given I uploaded the Screenshots for the AA17 Type-ins), though I feel they should be completely removed. The Orion Prime entry is a nice example, though I'm also concerned about how much editing was involved to get it looking like that and given that the entry for the Type-ins page would be subjected to future updates, the easiest approach seems like the best approach. Personally I prefer the approach I made on my Turbo Pascal Website, I did have to go to a bit of trouble initially to setup tables as such, but once their in place, adding additional stuff to the site isn't a problem.
I don't feel that they should be removed, for the same reasons that redbox has outlined. I just feel that they should be smaller!
It's really not that hard to create the gallery-style table; you can just use MediaWiki's built-in
<gallery> tag. Look at the source for the
Orion Prime entry, for example.
QuoteI like the idea of the instructions being on the Disk Image, I only wish I knew how I could get Protext to save straight out ASCII rather than Formatting it's own Gibberish on top of it, because of that I've been using the Turbo Pascal editor! ;)
Typing
PROG at the
Protext prompt switches it to "program mode". That should save the file as ASCII - although I think that any strange formatting characters used in "document mode" will remain. You may be able to write your own program to filter them out, though.
QuoteNot sure how renaming the files works, from memory I think I had to do just that, or perhaps it's a question of Deleting the Old File from the Wiki, renaming it on your computer and uploading it again.
I think deleting uploaded files is only possible by a select group of administrators - and I'm not sure who they are, or how to request deletion of a file should I wish to do so in the future! ???
Quote from: Nich on 19:39, 19 October 10
I don't feel that they should be removed, for the same reasons that redbox has outlined. I just feel that they should be smaller!
I totally agree that they shouldn't be removed; smaller is easy, you just use the thumbnail syntax...
It's up to the administrator, moderator, God on how to run the Typeins page (Not Me!! :( ). I'm only trying to get something onsite with the code and the Instructions for people to use. :P
I personally used to love typing in a program without any screenshots cause that was part of the fun of typing it in, in the first place! Surely nobody is interesed in a graphical demo once an Animated GIF is produced of it or a simple PNG, which kind of defeats the purpose of having Type-ins!
I don't think so - half of the fun (if not all of it) is actually typing it in, not for the result itself... otherwise, indeed, let's just build ready-built dsk images...
Gryzor wrote:
I don't think so - half of the fun (if not all of it) is actually typing it in, not for the result itself... otherwise, indeed, let's just build ready-built dsk images...
Well that settles that then.
I have spent this evening uploading all the type-ins from issues 5 to 12 of Amstrad Action and updating the AA Type Ins (http://cpcwiki.eu/index.php/AA_Type_Ins) entry with galleries of screenshots and links to the DSK files, and adding lots of extra bits of information about some of the type-ins, in a very anorak-like manner. ;)
Things begin to get confusing from issue 14 onwards, as AA began to publish listings outside the 'Type-Ins' section - and they didn't always give them names or mention who wrote them! ::) That'll be fun.
Thanks so much for your effort, mate...
Well, they're still type-ins. I don't think this should pose any real trouble :)
I have uploaded a screenshot and DSK file of the GIGO type-in from issue 13 of Amstrad Action.
Quote from: Nich on 21:18, 13 November 10
I have uploaded a screenshot and DSK file of the GIGO type-in from issue 13 of Amstrad Action.
Wow, I remember playing this on my friend's CPC464. The graphic is Max Headroom (http://en.wikipedia.org/wiki/Max_Headroom_%28character%29)!
The last time I thought of this was when my college lecturer was going on inanely about Garbage In Garbage Out. And that was a long time ago too :)
I have now added the Type-Ins for issues 16 and 18 of Amstrad Action, and the AA Type Ins (http://cpcwiki.eu/index.php/AA_Type_Ins) entry has been split up so that each issue of Amstrad Action now has its own entry - it was becoming far too large for one page! I have also created an Amstrad Action Type-Ins (http://www.cpcwiki.eu/index.php/Category:Amstrad_Action_Type-Ins) sub-category.
Great job with the splitting - it was indeed way too long!!!
Btw, what's the super-category of AA Type-ins?
@Nich: I've typed in several AA listings so far. Maybe you can upload them to the wiki. It seems you're familiar with wiki/html coding.
http://cpcwiki.eu/forum/index.php/topic,497.msg4203.html#msg4203 (http://cpcwiki.eu/forum/index.php/topic,497.msg4203.html#msg4203)
The reason for typing in "backwards" is simple: Some were faulty and bugfixes were released in later issues.
Quote from: Gryzor on 15:09, 23 December 10
Great job with the splitting - it was indeed way too long!!!
Btw, what's the super-category of AA Type-ins?
Type Ins (http://www.cpcwiki.eu/index.php/Category:Type_Ins). I feel that it should be Type-Ins, with a hyphen, but renaming a category will probably cause all sorts of chaos!
Oooh yes, I wouldn't touch it :D
Quote from: CPCIak on 15:27, 23 December 10
@Nich: I've typed in several AA listings so far. Maybe you can upload them to the wiki. It seems you're familiar with wiki/html coding.
http://cpcwiki.eu/forum/index.php/topic,497.msg4203.html#msg4203 (http://cpcwiki.eu/forum/index.php/topic,497.msg4203.html#msg4203)
I have now added the type-ins for issues 102-105 to CPCWiki. I'll look at issues 106-108 some other time (of course, it has nothing to do with reminding me how embarrassing some of my own type-ins are! :D)
I've typed out Madballs (not to be confused with the French game "Madball" which is on NVG), which is a pretty comphenensive game from AA63 (December 1990) and checked through it (via Pat McDonald's ROM dodgy "Typewriter" ;D ). Just thought I'd attach it here for the moment so nobody goes through the strain of having to Type it out again. I reckon it could even go into the Type-ins section in the Games Directory in NVG.
I just typed in the Sound Digitizer from AA15 but I'm getting a data error. I've scanned through the op codes twice and can't see which one is wrong. I got the program to print out the checksum it gets and it is 16 out (57855 instead of 87871) which indicates that one is out by a digit (e.g. C5 instead of D5 or something)
Could someone check it out with a fresh pair of eyes please?
Hi there.
I've had a bit of a perusal at the scans.
They are hard to read innit?
Anyway, I *think* the following need to be corrected in your listing (though I could be wrong!):
310 DATA 6E,BC,21,C6,91,CD,DE,90,3E,42
I reckon the C6 should be CB.
420 DATA ED,78,84,91,C9,21,86,91,CD,DE
The 78 could be 7B.
460 DATA 77,00,DD,23,18,7A,B3,20,EA,FB
The 18 could be 1B.
I hope that helps!
Fingers crossed, you're right. Its a shame the code was always hard to read in the magazines! I'll check it tomorrow when I'm on the machine with the source code and emulator :)
Nope, that got things up to 57866 but I guess I need to try re-readig with fresh eyes and a magnifying glass!
Edit: It's a big ask but is there a higher quality scan for page 27 of AA15? Some of the letters really are quite blurry and I don't think it's my eyesight!
Ok, here are AA15's type ins. The only problems are in Sound Digitizer (and Sound Sampler due to not being able to test it without Sound Digitizer) and Double Height Machine Code due to the code being slightly ambiguous on the scanned pages.
Quote from: betpet on 11:37, 08 April 11
Ok, here are AA15's type ins. The only problems are in Sound Digitizer (and Sound Sampler due to not being able to test it without Sound Digitizer) and Double Height Machine Code due to the code being slightly ambiguous on the scanned pages.
Unfortunately the Type-ins from AA15 have been done and are up on the Wiki (http://www.cpcwiki.eu/index.php/Amstrad_Action_December_1986_Type-Ins). :( Unfortunately their not marked (by issue number) on the page itself and the Issue number can only be seen from the AA Type-ins page (http://www.cpcwiki.eu/index.php/AA_Type_Ins). :(
*facepalm*
All that effort for nowt :(
I have uploaded instructions in plain text format for all the Amstrad Action type-ins from issues 5 to 20. I've had them for a while but I never got round to uploading them to CPCWiki until now!
I was also working on the type-ins and instructions for issues 22 to 24, but most of the work seems to have been deleted from my hard disk, so I am understandably not amused and I am not in the mood right now to type them all in again! >:(
Well, 15-20 is still awesome. Thanks for that :)
Great stuff! We'll get them done soon enough :)
Quote from: betpet* Thanks to DrMoreau for creating and hosting this!
Yes, but Imageshack images do not appear for everyone :(