Problems burning Kickstart

[DoogUK]

Cool, so i'm going to use 27c322's...they will do the trick?

I'm still learning on the eprom side of things.

[DoogUK]

I've taken out the original exec and replaced it with Piru's already as it's smaller than the original.

[Charlie]

Originally Posted by DoogUK

What line should i put in my startup to load the WB.lib?

Now then, what was it?
It's in my statup-sequence to add a new Ram-Lib. No, can't remember. I'll have to get back to you when I've fired-up my A1200.

Still, if you've going for a 1mb Rom I suppose it's a moot point anyway...
...nice to hear it can be done in software, no hardware butchery required - I had a feeling there was a little more to it, glad to be wrong.

[Toni Wilen]

Originally Posted by DoogUK

Hmmmm seems i can select 1mb rom before i start to build an KS image, will the A1200 automaticaly use all this area? or just the first 512kb?

Where's Toni when you need him

It does work but note that it won't work with Blizzard MAPROM feature.

http://eab.abime.net/showpost.php?p=...&postcount=219

(someday I really need to write my own "superrom" that supports compressed modules, automatically unpacks to RAM, including exec.library etc.)

[Calgor]

I will be making my own 1MB rom for my blizzard too! Maybe even tonight, of OS3.9BB2+scsi patch + 1mb rom extension + some other stuff that I can get to work. DoogUK, if I get far and u need any further assistance, jump on IRC.

Toni,
Is there anyway to get the 1MB ROM into RAM for faster OS function operations given that one can no longer use the Blizzard MAPROM function?

[DoogUK]

I'm guessing we could still softkick a 1mb image into ram..

[Toni Wilen]

Originally Posted by Calgor

Is there anyway to get the 1MB ROM into RAM for faster OS function operations given that one can no longer use the Blizzard MAPROM function?

Not without some kind of softkick and reboot but you don't need custom EPROM for that

It is possible to have ROM that includes special boot code that relocates the ROM to RAM but it gets really tricky because you need exec and expansion before you know where the fast RAM is located.. (and it will get even more trickier if you want exec in RAM too..)

[alexh]

Originally Posted by Toni Wilen

It does work but note that it won't work with Blizzard MAPROM feature.

Going slightly off topic, how does the Blizzard MAPROM (or any MAPROM) feature work? Does it run a small program on a ROM which performs the copy and sets the MMU to redirect accesses? Is the reason the MAPROM only works for 512Kbyte images a feature of the accelerators firmware?

[Toni Wilen]

Originally Posted by alexh

Going slightly off topic, how does the Blizzard MAPROM (or any MAPROM) feature work? Does it run a small program on a ROM which performs the copy and sets the MMU to redirect accesses? Is the reason the MAPROM only works for 512Kbyte images a feature of the accelerators firmware?

I don't know how it copies the ROM (there is no copy code in 68060 boot rom) but it is some kind of Blizzard memory controller trick. MMU is not used or even needed.

[DoogUK]

I've just built a 1mb rom image..and as stated Piru's exec is at the start. Winuae displays a black screen with no cpu usage registering...so i guess thats a no go.

What rom base address do i need for the 1mb rom Toni?

[Toni Wilen]

Originally Posted by DoogUK

I've just built a 1mb rom image..and as stated Piru's exec is at the start. Winuae displays a black screen with no cpu usage registering...so i guess thats a no go.

What rom base address do i need for the 1mb rom Toni?

I don't think you can create single file 1M ROM with remus. (1M option creates 1M ROM without "memory hole")

AFAIK you need to create 2 ROM files, one at 0x00E00000 and another at 0xF80000.

0xF80000 needs the patched exec. Fill 0x00E0000 ROM with modules that don't fit in "normal" KS ROM space.

Then join the files (E0+F8) together.

[alexh]

Interesting workaround, would it not add headers and things?

I wonder if doobrey could easily add this option... are you reading??

[Calgor]

DoogUK and I have been discussing this 1mb rom on IRC. Magic thread for those interested: http://www.amiga.org/modules/newbb/v...=34437&forum=9

Someone has successfully made 1mb rom and you need to use that special more recent version of Remus along with other special instructions (assuming you don't want to use cd32 exec but 1mb rom patch module instead)

[alexh]

Oooo...

http://www.doobreynet.co.uk/beta/Remus_1-rc7.lha

That thread is from a long time ago... I wonder if this is the latest version...

[DoogUK]

Which i cannot get to run .

It seems you have to patch the exec, create a 1mb rom with the extended part at the front with the right rom headers, insert romheader and WBstart.lib into the rom image and you should be thereabouts.

[DoogUK]

hmmm pretty much got the rom image built but i dont know what to do with the romheader...it's not accepted as a module and there's no instructions with it.

[DoogUK]

Giving up for today, i just cannot get the beta version of remus running which is the one you need to build the extended rom

[DoogUK]

I have created the 44.57 roms though and they work perfectly in winuae

[DoogUK]

Ok, after being back and forth with Doobrey who a should add is extremely helpful and i must express my appreciation .

He has updated his remus/romsplit and has included all the necessary patches to create the 1mb rom.

Its made the whole process a lot easier and faster but there's still a few steps to overcome, i have created the rom in 2 parts, both are split into hi and lo parts themselves.

Doobrey has compiled an Arexx script to join the roms together to create the full 1mb rom, which i cannot get to run pilot error i suspect but i'm waiting to hear back from Doobrey.

Just one question for Toni, does winuae support loading 1mb roms?


For anyone interested the new remus/romsplit archive is here:
http://www.doobreynet.co.uk/beta/index.html

[Doobrey]

Originally Posted by alexh

I'd like to know if you can add things like; cfd the CF card driver which would allow you to boot from CF card with no hard drive?

CFD is safe to put in ROM,but you can't boot from it (yet )
i. There's no code in compactflash.device to find the RDB,load filesystems and mount partitions
ii. The device uses a couple of dos.library functions.. but dos won't be available at boot time (and it also doesn't check for failure when it tries to open dos!)

I'd also be curious to know what adding/replacing files to the KS ROM does to RAM usage. Obviously the more things you put in there... the more things get loaded into RAM on power on?

In the case of adding updates from the Amiga OS ROMupdates, it should mean less RAM use, since they're run from ROM instead of being loaded into memory by Setpatch.