What's Coyote Flash got against OS3.1? Good now, but...

[K7HTH]

I have decompressed the latest firmware of Coyoteflash1.6 onto a floppy on my A2000HD. The program executed fine from the floppy under OS3.9 on the A2000HD. I tried to install it on my A4000D loaded with WB3.1. The Coyote Flash icon, after placing the drawer onto the HD, will not execute. It flickers a momentary window then nothing. I have 12MB of fast RAM on the mobo with 2 MB Chip, RAM is not the issue here. So I ask again, "What's Coyote Flash got against OS3.1?"

[Doobrey]

Daft question, but does your A4000 have a kickflash board?
Maybe it checks to see if one is present, and quits if it can`t find it.

Failing that, does anything show up from snoopdos?

[K7HTH]

Doobrey wrote:
Daft question, but does your A4000 have a kickflash board?
Maybe it checks to see if one is present, and quits if it can`t find it.

Failing that, does anything show up from snoopdos?

emmmm, well, yes, I have the KFOS4 card in the A4000D. I posted the Q because when running the CF program with OS3.9 in the A2000HD, the program would execute and post a comment that the card cannot be found if the former is not installed when attempting to load the program. Hence, I revert to my previous question.

Snoopdos. I will have to reasearch what that is; thanks for commenting.

[K7HTH]

Thankfully, persistence pays. Four hours later Switching the executable file from an earlier version with the latest firmware version yielded recognition of the Kickflash in my A4000D. I loaded the firmware and kickstart 3.1 from mirror to flash then pulled the jumper and rebooted. A change is now the ROM pauses long enough to allow the IDE HD to spin up and load the WB by passing the OS3.0 kickstart floppy. So I can assume the kickflash worked. Now what puzzles me is in the ShowConfig program my kickstart rom is 512KB and still 39.126 the same as it was without the KF and booting with 3.0 ROMS. I guess I won't know for sure if 3.1 ROMS have been established when I can finally get my CDROM drivers configured and attempt to load OS3.9. I hope to attempt to install my Picasso IV in WB3.1 before then. That too should confirm if KS3.1 installed; any thoughts?

[Doobrey]

Sorry if it sounded a daft question earlier, I just didn`t understand which amiga the kickflash boards was in.

Does the 'About' menu on workbench give you a different kickstart revision? (and is 512kb of ram missing?)
 Try typing 'version exec.library' at a cli, it should say something like 'exec.library 40.10' if it`s managed to kick into the 3.1 roms, otherwise it`ll say v39.47 for the 3.0 roms.
BTW, what CPU card is installed?

[K7HTH]

Doobrey wrote:
Sorry if it sounded a daft question earlier, I just didn`t understand which amiga the kickflash boards was in.

Does the 'About' menu on workbench give you a different kickstart revision? (and is 512kb of ram missing?)
 Try typing 'version exec.library' at a cli, it should say something like 'exec.library 40.10' if it`s managed to kick into the 3.1 roms, otherwise it`ll say v39.47 for the 3.0 roms.
BTW, what CPU card is installed?

Thanks for the info. Cli reports 39.47 for exec.library and 40.42 for version.library. So does this mean my Kickflash did not successfully load KS 3.1??

[adolescent]

Which kickflash firmware version are you using?  Also, what are your system specs?  (accellerator, etc.)

Also, during setup did you tell Kickflash to activate only when a KS3.1 rom was found?  

[K7HTH]

adolescent wrote:
Which kickflash firmware version are you using?  Also, what are your system specs?  (accellerator, etc.)

Also, during setup did you tell Kickflash to activate only when a KS3.1 rom was found?  

I am using Firmware version 1.6 with an A4000D powered with a 3640 25MHz processor with 2MB chip and 12 MB fast RAM with 3.0 ROMS. I answered 'No' on the 3.1 question to only activate when 3.1 ROMS are detected because I have 3.0 ROMS and purchased the Kickflash OS4 from Red to work 3.1 ROMS for my A4000D. If this card cannot handle the 3.1 Kickstart then what good will it be for OS4?

A thought: if Kickflash can contain the 3.1 kickstart and load WB as such, then can one remove the existing system ROMS while a (working) kickflash is installed?

[K7HTH]

Top

[K7HTH]

Anyone else have these similar symptoms with their Kickflash OS4?

[adolescent]

KD7HTH wrote:
I am using Firmware version 1.6 with an A4000D powered with a 3640 25MHz processor with 2MB chip and 12 MB fast RAM with 3.0 ROMS. I answered 'No' on the 3.1 question to only activate when 3.1 ROMS are detected because I have 3.0 ROMS and purchased the Kickflash OS4 from Red to work 3.1 ROMS for my A4000D. If this card cannot handle the 3.1 Kickstart then what good will it be for OS4?

Early versions didn't support ROM mapping.  Since you are using 1.6 it should work.  

The Kickflash works great for it's intended use.  I think the ROM mapping is just an extra feature.  I have all of my rom patches loaded and some other programs before boot.  It's normally a slow, 2 reboot process on standard OS3.9 but now it's done at cold start without a single reboot.  

That said, where did you get your Kickstart image?  Are you sure they're correct and working?  (ie. try with BlizKick, etc.).  

Best thing to do is get KS3.1 ROMS.  That way you don't have to go through all of this and it will work right away.

A thought: if Kickflash can contain the 3.1 kickstart and load WB as such, then can one remove the existing system ROMS while a (working) kickflash is installed?

I don't think so.  Removing the Kickstart roms would likely result in a non-functioning computer.

[Peyote]

Hi,

Please send me an email (info@coyoteflux.nl) and I will send you an other version which should fix it. The problem is related to the A2000 and is caused by a flag set in the memory allocation. Thanks in advance!

Best regards,

Sharwin Raghoebardayal
www.coyoteflux.nl

[Peyote]

Hi again,

What kind of CPU card are you using?

The Kickstart remapping works only with Blizzard, CyberStorm and Commodore A3640 (and compatible) cards.

If you are having problems with the CoyoteFlash executable, I will send you a version that can fix it.

Best regards,

Sharwin Raghoebardayal
www.coyoteflux.nl

[K7HTH]

Peyote wrote:
Hi again,

What kind of CPU card are you using?

The Kickstart remapping works only with Blizzard, CyberStorm and Commodore A3640 (and compatible) cards.

If you are having problems with the CoyoteFlash executable, I will send you a version that can fix it.

Best regards,

Sharwin Raghoebardayal
www.coyoteflux.nl

Thank you. My email is tofuss@yahoo.com My KickflashOS4 is brand new from Redrumloa. I am using it in an A4000D with a C= A3640 with stock 3.0 ROMS. The KS 3.1 file I received from a friend who claims his KickflashOS4 works great in his A4000D. Like I said before since I loaded the KF with KS 3.1 and firmware1.6, the 3.0 screen is gone and the boot time is longer allowing the HD to boot first. But when I look in Cli for versions of exec.library I still see 39.47, not good; 'mission not accomplished Jens.'

Regards,

-Ken

[Peyote]

Hi,

Actually this has nothing to do with Jens. There are many different configurations and with lowlevel apps such as this it can give a conflict on some systems.

I have an A4000D/KS3.0/A3640 here that works well with the card, but will try to reproduce the problem and fix it. Could you send me your mirrorfile (the contents of your Flash)? Thanks in advance.

Best regards,

Sharwin Raghoebardayal
Coyote Flux
www.coyoteflux.nl