English Amiga Board


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 25 April 2023, 20:52   #1
BlackByte
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
BlackByte is offline  
Old 01 May 2023, 12:52   #2
Toni Wilen
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)
Toni Wilen is offline  
Old 02 May 2023, 17:50   #3
BlackByte
Registered User
 
Join Date: Aug 2014
Location: German
Posts: 47
Hey Toni,

many THX, i love you

The WinUAE German Translator ;-)
BlackByte is offline  
Old 03 May 2023, 10:41   #4
SpaceAce
Registered User
 
SpaceAce's Avatar
 
Join Date: Jul 2020
Location: Bunbury/Australia
Age: 55
Posts: 27
Quote:
Originally Posted by BlackByte View Post
many THX, i love you



I don't have a THX compatible amp. Can you repost that in DTS?
SpaceAce is offline  
Old 03 May 2023, 13:00   #5
Retroplay
Lemon Curry ?
 
Retroplay's Avatar
 
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 },
The rom in your archive has a crc of f248ad3c.

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.
Retroplay is offline  
Old 03 May 2023, 16:36   #6
rhester72
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
rhester72 is offline  
Old 07 May 2023, 14:25   #7
TheEdge
Registered User
 
TheEdge's Avatar
 
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.
Attached Thumbnails
Click image for larger version

Name:	IMG_0281.jpg
Views:	78
Size:	577.3 KB
ID:	78907  
TheEdge is offline  
Old 07 May 2023, 14:29   #8
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
Quote:
Originally Posted by Retroplay View Post
@Toni
Got a question about "Microbotics HardFrame v1.9", it doesn't seem to be recognised by WinUAE rom scan.
Archive had old wrong version.

Quote:
Originally Posted by rhester72 View Post
Sorry, been playing catch-up for a bit...I assume the following two are still MIA?

Microbotics HardFrame v1.8
TekMagic 2040
Both are already dumped. v1.8 was added in 4.4.0 (but it was not included with the archive until now for some reason). 2040 was added very recently.

Quote:
I've got an ICD Advantage 2000 SCSI card with v2.01 rom on the board.
Replying soon. Odd timing because I was replying to earlier 2 posts just now, before your post had appeared..
Toni Wilen is offline  
Old 07 May 2023, 17:29   #9
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
Quote:
Originally Posted by TheEdge View Post
@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.
What does "version icddisk.device" return? There is already unknown 2.x dump that has v33 icddisk.device. (2.2 is v34)

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")
Toni Wilen is offline  
Old 07 May 2023, 19:06   #10
TheEdge
Registered User
 
TheEdge's Avatar
 
Join Date: Nov 2022
Location: Toronto/Canada
Age: 54
Posts: 15
Quote:
Originally Posted by Toni Wilen View Post
What does "version icddisk.device" return? There is already unknown 2.x dump that has v33 icddisk.device. (2.2 is v34)

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")
I followed your instructions and attached my dump of v2.01 rom which has v32.1 icddisk.device. The board address was $e90000. Not sure it worked.
Attached Files
File Type: zip rom.bin.zip (11.1 KB, 62 views)

Last edited by TheEdge; 07 May 2023 at 19:19.
TheEdge is offline  
Old 07 May 2023, 19:38   #11
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
Quote:
Originally Posted by TheEdge View Post
I followed your instructions and attached my dump of v2.01 rom which has v32.1 icddisk.device. The board address was $e90000. Not sure it worked.
Thanks, it works. It needs "header" from other dump because first part of ROM is partially shadowed by IO space. (both v33 and v34 have same header so v32.1 probably also have same). Reading it fully requires rom reader.

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..
Toni Wilen is offline  
Old 07 May 2023, 20:55   #12
muchacha_grande
Registered User
 
Join Date: Jan 2017
Location: Haedo/Argentina
Posts: 7
Quote:
Originally Posted by rhester72 View Post
Sorry, been playing catch-up for a bit...I assume the following two are still MIA?

Microbotics HardFrame v1.8
TekMagic 2040

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.
muchacha_grande is offline  
Old 08 May 2023, 17:39   #13
rhester72
Registered User
 
Join Date: Feb 2008
Location: New York / USA
Posts: 360
Quote:
Originally Posted by muchacha_grande View Post
So, do you have MacroSystem DraCo Boot ROM v1.3 ?
In my case is the only one missing
No. Nobody has it because it contains copyrighted and licensed Kickstart code.
rhester72 is offline  
Old 09 May 2023, 19:06   #14
muchacha_grande
Registered User
 
Join Date: Jan 2017
Location: Haedo/Argentina
Posts: 7
Well, knowing that reduces the pressure on my hunt. :-)
Thank you.
muchacha_grande is offline  
 


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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 11:43.

Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Page generated in 0.08805 seconds with 16 queries