Meetup in Denmark V.3.0

  • Thread starter Thread starter TroelsDK
  • Start date Start date
  • Replies Replies 67
  • Views Views 1599
Yes I forgot Rollerball too! ha! Cheers Troels :) Will play them a bit to get better at them :)

And the Amiga Mugs!! YES!! Will get a few of those to fill my cupboard up. Quite awesome.

Zig is very happy for the mini Megadrive you gave him, he said Tusind Tak :)


BTW, Demolition, you may be interested to know that when I swapped my Flash Kicks back to the good old EPROM my mega demos that seemed to be running like my machine suddenly downgraded to an 030 are all now running smooth again, well, alot smoother, how you'd imagine for 060.

More testing on the Flash needed I think. I'm not quite sure if its a module issue (something I missed when compiling in remus, or wrong version) or the flash itself. Its also booting slower now again and its not intermittent like it was (its booting marginally quicker with flash, main point is between ROM initialization and HDD starting). Basically replacing the Flash back for EPROM has eradicated all the issues I had at the meetup and the old girl is running fine again.

My Amiga defies all logic at times, that's why I love it! :D
 
Last edited:
Doesn't seem likely that it should be the flash itself causing those performance issues. You could do a transrom with both the flash and the EPROM installed and compare the checksum of the two files if they are supposed to be identical. But anyway nice to hear that you found the problem.

I have a feeling that there's a fine line between love and hate in that relationship. :)
 
Thanks for the advice :) the Kick on flash will show differently as it has 2x 3.1 kick combined to it. I combined my HI and LO 3.9 of 512K to 2x 3.1 of 256K to make 1MB for each Flash. Similar to how one would make a dual switched A600 3.1 to 1.3 (combining 3.1+1.3+1.3) to fill the space correctly. this is only because my original intention was to have the lower part of flash boot 3.9 and the upper part boot 3.1. The extra 3.1 image was just to fill the space and make the whole image 1MB. I did a similar thing with success on my sons A600, but using EPROM, not flash.

I'm going to just image my 3.9 on its own next without combining and see how it runs in exactly the same conditions as my current 3.9 EPROMs. then go from there. I took two many steps in one go.

And yeah, some days I really hate my Amiga too. It wouldn't be normal if I didn't :D
 
The reason for using transrom is that it will reveal how the Amiga sees the contents exactly, irrelevant of how you stored the contents in the flash memory space.

I was also planning to make a 1.3+3.1 ROM for my A600, however I don't yet know if it should be plain or customized. It could also be possible to use a 2MB ROM and get room for 1.3+2.05+3.1, however I don't really see the reason for having 2.05 if it has 3.1. :)
 
Ah ok, I misunderstood what transrom was doing :)

Yeah, just go for 1.3 3.1, no need for 2.05 I don't think. plain 1.3 with Custom 3.1 could be fun to try! depends what you want to do with your A600.
 
The main reason for patching 3.1 would be to have an updated scsi.device in it so it could support larger drives. Haven't tried it yet and only read a little about it, but I think that should be the way to go for larger drives?
 
Thats a good point, I use cosmos' beta scsi.device. Be aware of filesystem incompatibilities, pfs for example, doesnt work on some variants. I use sfs 1.279 and find its generally ok.

Sent from my LT15i using Tapatalk 2
 
You must log in or register to reply here.

Similar threads

TroelsDK
Meetup in Denmark 2nd edition
2
Replies
22
Views
630
TroelsDK
TroelsDK
Phipscube
Meetup in Denmark
2 3
Replies
58
Views
915
johnim
johnim
Back
Top Bottom