Welcome, Guest. Please login or register.

Author Topic: Catweasel S-class and WHDLoad conflict.  (Read 3966 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline EdKing

  • Full Member
  • ***
  • Join Date: Jul 2004
  • Posts: 163
    • Show all replies
Re: Catweasel S-class and WHDLoad conflict.
« on: September 14, 2004, 11:17:24 PM »
None of the Buddha software will cause WHDLoad not to work. I have a Buddha in my
system and WHDLoad works fine. It must be something in the Catweasel software
causing your problem. Look in the WBStartup drawer and maybe in the devs:dosdrivers
to see if the Catweasel put anything there.

Ed King
 

Offline EdKing

  • Full Member
  • ***
  • Join Date: Jul 2004
  • Posts: 163
    • Show all replies
Re: Catweasel S-class and WHDLoad conflict.
« Reply #1 on: September 14, 2004, 11:44:43 PM »
One more thing I thought of, do you have the Catweasel hooked up to your Amiga floppy,
or floppy connector on the motherboard ? Maybe the Catweasel is sending a hardware
interupt that way and it's messing up WHDLoad that way.

Ed King
 
 

Offline EdKing

  • Full Member
  • ***
  • Join Date: Jul 2004
  • Posts: 163
    • Show all replies
Re: Catweasel S-class and WHDLoad conflict.
« Reply #2 on: September 15, 2004, 11:37:33 AM »
Quote

From the motherboard a floppy a cable goes to Kylwalda boot adapter, then this adapter chains to Catweasel.


This would be my guess as to your problem. Same reason Amiga drives click with no floppy in them. The Catwaesel/Kylwalda combo is sending a drive seek interupt and messing up WHDLoad. Did you try running your games with a blank floppy inserted in the drive ? It is a longshot but it might work, or maybe one of the noclick utils.

Ed King