25 April 2023, 20:52 | #1 |
Registered User
Join Date: Aug 2014
Location: German
Posts: 47
|
expansion_boot_roms
I have a question, is the expansion_boot_roms.zip file no longer up-to-date? Didn't find anything under Zone Thanks
|
01 May 2023, 12:52 | #2 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
Uploaded. I think only changes are early (68040 only) GVP 2040 ROM image and CSMK1 ROM was split (68040 has only SCSI ROMs, 68060 variant has separate 68060 "early boot" ROM chips and SCSI ROM chips)
|
02 May 2023, 17:50 | #3 |
Registered User
Join Date: Aug 2014
Location: German
Posts: 47
|
Hey Toni,
many THX, i love you The WinUAE German Translator ;-) |
03 May 2023, 10:41 | #4 |
Registered User
Join Date: Jul 2020
Location: Bunbury/Australia
Age: 55
Posts: 27
|
|
03 May 2023, 13:00 | #5 |
Lemon Curry ?
Join Date: Sep 2004
Location: Denmark
Age: 49
Posts: 4,079
|
@Toni
Got a question about "Microbotics HardFrame v1.9", it doesn't seem to be recognised by WinUAE rom scan. According to your code in rommgr.cpp - the checksum is different. Code:
{ _T("Microbotics HardFrame v1.9"), 1, 9, 1, 9, _T("HARDFRAME\0"), 32768, 256, 0, 0, ROMTYPE_HARDFRAME, 0, 0, NULL, 0x948a3de8, 0xc34cb0ef, 0xa0ebdd71, 0x9d604d38, 0x625a160d, 0x9e2ca95d, NULL, NULL }, I've put a different dump in the zone with a crc of 948a3de8 in the zone, which is recognised. Only two differences when checked against each other at 0x20 and 0x40 in hex editor. |
03 May 2023, 16:36 | #6 |
Registered User
Join Date: Feb 2008
Location: New York / USA
Posts: 360
|
Sorry, been playing catch-up for a bit...I assume the following two are still MIA?
Microbotics HardFrame v1.8 TekMagic 2040 |
07 May 2023, 14:25 | #7 |
Registered User
Join Date: Nov 2022
Location: Toronto/Canada
Age: 54
Posts: 15
|
@Toni
I've got an ICD Advantage 2000 SCSI card with v2.01 rom on the board. Is this rom wanted for archiving. If so what can I use to dump it. Heres a pic of the board. |
07 May 2023, 14:29 | #8 | |||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
Quote:
Quote:
Quote:
|
|||
07 May 2023, 17:29 | #9 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
Quote:
ROM location is $e98000 to $e9ffff (assuming you don't have other Z2 expansions, if you have more, use for example with WB disk tools/showconfig or sysinfo to check board's base address and add $8000 to get ROM base address) Use any monitor program to save ROM address space, for example mon165.lha from aminet ("] e98000 8000 ram:rom.bin") |
|
07 May 2023, 19:06 | #10 | |
Registered User
Join Date: Nov 2022
Location: Toronto/Canada
Age: 54
Posts: 15
|
Quote:
Last edited by TheEdge; 07 May 2023 at 19:19. |
|
07 May 2023, 19:38 | #11 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
Quote:
This probably means previously unknown v33.0 is v2.1 because v34.0 is v2.2 and your version is v32.1. v2.0 most likely is v32.0. v1.6 is also dumped which unexpectedly has v1.0 device driver. Lots of versions.. |
|
07 May 2023, 20:55 | #12 | |
Registered User
Join Date: Jan 2017
Location: Haedo/Argentina
Posts: 7
|
Quote:
So, do you have MacroSystem DraCo Boot ROM v1.3 ? In my case is a missing one Last edited by muchacha_grande; 04 January 2024 at 22:21. |
|
08 May 2023, 17:39 | #13 |
Registered User
Join Date: Feb 2008
Location: New York / USA
Posts: 360
|
|
09 May 2023, 19:06 | #14 |
Registered User
Join Date: Jan 2017
Location: Haedo/Argentina
Posts: 7
|
Well, knowing that reduces the pressure on my hunt. :-)
Thank you. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Expansion_Boot_Roms.zip | sigma63 | request.Other | 3 | 12 June 2022 23:53 |
|
|