Al-Strad
Guild Adventure Software, The 
, Rhinosoft 1985
- Aka:
- Alstrad
- Language:
- English
- Authors:
- Paul Gill
- Systems:
- BASIC , PAW
- Platforms:
- Amstrad CPC , C64/128 , Spectrum
- Entered by:
- Alex, Eriorg, Gunness, Strident
- Added:
- 10-05-2010
- Edited:
- 25-04-2025
Synopsis
In the far off kingdom of Megabyte there lived a King called Kilobyte who rules peacefully over his land.
All was happy and fine until one dark night when the evil SINK appeared intent on causing trouble.
He crept into the castle and kidnapped the beautiful Princess Sally Software.
A hefty reward was put up by the King to anyone who could rescue his daughter.
It came to pass that a poor peasant by the name of AL_STRAD came to know of the challenge and decided this was his big chance.
Either he was exceptionally brace or just plain stupid, but he accepted the challenge to search out SINKS LAIR and rescue the damsel in distress.
Notes
Originally an Amstrad game by Paul Gill, written in BASIC.
The C64 (ported by Amir Latif) and Amstrad versions were released by Rhinosoft, whereas the Spectrum version (probably ported by Tony Collins) was released much later by The Guild.
The Spectrum port was produced using the PAW.
Resources (Upload file)
- Solution
- by terri
- Map
- by nimusi
- Further Info:
- Search at CPC-Power
- Search at Gamebase64
- Search at Museum of Computer Adventure Game History
- Search at Spectrum Computing
- Search at The Tipshop
- Search at World of Spectrum
[+] Users who have solved this game
[+] Users currently playing this game
Decided to try this after reading a good review in Gareth Pitchford's 'Twilight Directory' from Amazon.
Nice little game, with varied puzzles and locations, even if it can't seem to make up it's mind whether it's fantasy, magic or science fiction.
The puzzles are fairly easy, although a lot of backtracking is needed. There is only one puzzle that I thought was unfair (the force field). After struggling with this for some time I left it and carried on with the rest of the game. When I went back to the force field it had disappeared, with no indication of how or why. I eventually figured out why, but it would have been helpful to have a message on the action that triggered the change.