Welcome, Guest. Please login or register.

Author Topic: Dragon's Lair Woes  (Read 1885 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Dragon's Lair Woes
« on: November 02, 2010, 07:21:28 PM »
Hi guys,

So, today I received a copy of Dragon's Lair: Escape From Singe's Castle. A game I had the chance of picking up when I was a kid, but thought you needed the first game in order to run it, so turned it down.

Having just got back from work to find it sitting waiting for me I've just installed it with no problem whatsoever, however when it comes to pressing the 'Play' button the game just freezes. The same things happen when running the game from the floppy drive.  I've tried various options such as turning the sound and mirrored rooms off and on but I still end up at the same point.

Does anybody know of a solution to this? I'm trying to run it on my A600.

Kind regards,

Phil
 

Offline orb85750

  • Hero Member
  • *****
  • Join Date: Aug 2007
  • Posts: 1237
    • Show only replies by orb85750
Re: Dragon's Lair Woes
« Reply #1 on: November 02, 2010, 07:44:27 PM »
I've definitely had some game compatibility issues with both my OS2 (sold it) and my OS3 A600.  (Unfortunately, I cannot get my Escape game to work at all on any computer because of a disk error.)
 

Offline Cammy

Re: Dragon's Lair Woes
« Reply #2 on: November 02, 2010, 07:47:13 PM »
Try re-installing the game using WHDLoad instead:

http://whdload.de/games/DragonsLair.html
http://whdload.de/whdload/WHDLoad_usr_small.lha

Hopefully that should fix it so it works.
A1200 030@28Mhz/2MB+32MB/RTC/KS3.1/IDE-CF+4GB/4-Way Clockport Expander/IndivisionAGA/PCMCIA NIC
A1200 020@14Mhz/2MB+8MB/FPU/RTC/KS3.0/IDE-CF+2GB/S-Video
CD32 020@14Mhz/2MB+8MB/RTC/KS3.1/IDE-CF+4GB
A600 030@30Mhz/2MB+64MB/RTC/IDE-CF+4GB/Subway USB/S-Video/PCMCIA NIC/USB Numeric Keypad+Hub+Mouse+Control Pad
A500 000@7Mhz/512kB+512kB/ROM Switcher/KS3.1+1.3/S-Video

Get AmigaOS
 

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Re: Dragon's Lair Woes
« Reply #3 on: November 02, 2010, 07:56:50 PM »
Thanks Cammy, I'll give that a shot. I've had trouble getting things running using WHDLoad on my A600 but i'll give it a go :)
 

Offline delshay

  • Hero Member
  • *****
  • Join Date: Mar 2004
  • Posts: 1009
    • Show only replies by delshay
Re: Dragon's Lair Woes
« Reply #4 on: November 02, 2010, 07:58:43 PM »
if i remember it needs kickstart 1.3 to work correctly maybe WHDload can fix it to work on kickstart 2.0 and above. the link above in this thread is for the very first dragon's Lair which works ok but not for your version. you have the second part of the original game.
« Last Edit: November 02, 2010, 08:06:34 PM by delshay »
-------------
power is nothing without control
 

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Re: Dragon's Lair Woes
« Reply #5 on: November 02, 2010, 08:36:42 PM »
Okay, so I've copied over the two lha's however when I try ciicking on install I just get the can't open tool error.

Any ideas?
 

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Re: Dragon's Lair Woes
« Reply #6 on: November 04, 2010, 02:34:08 PM »
UPDATE

I had no joy with WHDLoad, so what I've ended up doing is picking up a 1.3 Kickstart and ROM Switcher from Amigakit (very speedy, thanks guys).

With this installed the game runs fine (and Darkseed loads at its intended resolution without changing it manually which is an added bonus).

The only issue now is that the 1.3 ROM doesn't recognise the A600's hard drive. Is there any way I can change this so that I can run the game from hard disc?
 

Offline save2600

  • Hero Member
  • *****
  • Join Date: Jul 2006
  • Posts: 3261
  • Country: us
    • Show only replies by save2600
Re: Dragon's Lair Woes
« Reply #7 on: November 04, 2010, 02:41:48 PM »
You need to patch the scsi.device into your Kickstart:

http://www2.gup.jku.at/~tkoeck/kick1.3_scsi.device_patch/

...not sure if there's an easier way to do it on your system without a MMU.
 

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Re: Dragon's Lair Woes
« Reply #8 on: November 04, 2010, 02:53:39 PM »
Thanks for that.

Sadly I think that may be a little beyond my ability.
 

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Re: Dragon's Lair Woes
« Reply #9 on: November 04, 2010, 03:41:47 PM »
@save2600

I downloaded GETSCSI11 from aminet, but how do I run it?  I couldn't find clear instructions in the guide it comes with.
 

Offline save2600

  • Hero Member
  • *****
  • Join Date: Jul 2006
  • Posts: 3261
  • Country: us
    • Show only replies by save2600
Re: Dragon's Lair Woes
« Reply #10 on: November 04, 2010, 04:39:37 PM »
Quote from: Philski;589321
@save2600

I downloaded GETSCSI11 from aminet, but how do I run it?  I couldn't find clear instructions in the guide it comes with.

I just tried it on my A3000. You have to open a shell/cli, point to the directory and then simply type getscsi. It's an executable that extracts the info from Kickstart and creates a scsi.device driver which was placed in the same directory. The guide included shows how to append it to your startup-sequence or userstartup file located in S.
 

Offline PhilskiTopic starter

  • Jr. Member
  • **
  • Join Date: Jan 2009
  • Posts: 64
    • Show only replies by Philski
    • http://gallery.me.com/phil.cobley
Re: Dragon's Lair Woes
« Reply #11 on: November 04, 2010, 05:26:41 PM »
Thanks for that! :) Okay, so I've created scsi.device, copied it to the devs directory on a backup workbench disk and edited the startup-sequence to match the one listed in the guide.

However, when trying to boot I get an error message telling me the device can't be recognized.

I've tried altering the startup from 'Dh0:' to 'System:' and 'Work:' but I still get the same message.

Any ideas?