eFlash 4000 (2mb version) and OS 3.9

[platon42]

Kristian95 wrote:
Ok, I have the card installed. I flashed it with the Kickstart update and added the following Blizkick modules:
NoClick, SpeedyChip, SpeedyIDE.

I noticed that the floppy drives still click. How do I make Blizkick modules work with an eFlash card?
Will SpeedyChip and SpeedyIDE do any good in my A4000T (I use the IDE controller on the motherboard)?
Any other suggestions as to what I should put in the eFlash card?

AFAIK the eFlash cannot cope with BlizKick modules or patches.

Using my NoClick module is kinda "pirating", but this is not the first time I have to provide for the lacks of Elbox.

SpeedyIDE is a BlizKick patch to the ROM (MapROM) and won't work with either flashrom hardware directly, especially because the ROM Update will include an updated IDE-Device. You can however, easily apply the SpeedyIDE patch to the IDE-Devices in the AmigaOS Rom Update file using a hex editor.

And regarding your IDE controller in your A4000T: You *really* should go for an IDE->SCSI adapter and use the SCSI controller in your A4000T which provides a speed of nearly 10 MB/sec without CPU load instead of 2.3 MB/s (2.6 MB with SpeedyIDE) with 100% CPU load.

SpeedyChip is obsolete with 68060 libraries >V42.

[platon42]

Kristian95 wrote:
@adolescent

I tried putting the NoClick from Lucifern in my eFlash but that didn't work either. I've for now installed DosPrefs and that helps once WB is booted.

It could be that the eFlash doesn't support DOS-Hunks from Kick 2.0 (e.g. DREL16), you might need to use "StripHunk RELOC32" on the file before it works in the eFlash.

@adolescent:

[ ] You do understand that Luciferin is commercial software package for competitive products by E3B (Highway+Romulus, Algor (Pro) and Deneb) and that using parts of it for Elbox products without owning the E3B product may be considered pirating.

Probably you don't see this, but your sort of people didn't care about the P96 violation by Elbox or the RDB issue either.

[platon42]

wawrzon wrote:
as already stated eflash doesnt seem to support patching amiga roms which is just too bad, cause i cant see what other it would be good for.

E3B Flashrom products can incorporate custom Kickstart images (e.g. created with RomSplit/Remus for use with a tailored BlizKick romtag. Using this "3.9++" Rom with fixed rom bugs, speedramsey, noclick, alert patch, etc. every day.

[platon42]

wawrzon wrote:
@platon42:
by the way, if im going to get something from e3b in the near future it will sure be deneb. as you are part of the project, the question i would have is: will its flashrom be able to hold the modified kickstart available at a cold boot too?

If you got a board with MapROM feature (e.g. phase5 boards), sure (there are no other means for a Zorro board to directly mirror the kickstart image at 0xf80000). This works with the Algor and the Romulus already, too. The 4 MB of user flashrom is big enough to hold plenty of stuff (e.g. to boot MorphOS PowerUp).

[platon42]

wawrzon wrote:
platon42: thank you. this might be the solution then, since i got the csmk1'S. the only thing i mistrust a little is mirroring and holding the updated rom in the memory since it seems to cause problems with warm-resets, so maybe i would still have to look @ some replacement that fits in the kickstart socket as alternative

I also have a CS 060 MK I and have no problems with it whatsoever. The RAM on the mainboard that is used for the shadow kickstart image is write protected right after copying and stays this way even across reboots. I've had hardly any problems that would require turning off the machine (there are other and by far worse stability problems created by mechanical fit problems in my machine currently).