![]() |
![]() |
#1 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
AMAX problems
I tested A-Max 2.56 with GVP emulation using v1.6 of gvpscsi.amhd. A-Max should automatically detect the AMAX0 partition, and on booting the emulated Mac, the Mac should ask whether you want to format it.
On booting a System 6.0.8 floppy disk (A-Max format, extended ADF), the desktop appears and you get the do-you-want-to-format prompt for the RAM disk. But the system kind of hangs after that (you can still move the mouse pointer). Log output: Code:
SCSI command EE, no direction specified! UAEHF: unsupported scsi command 0xEE LUN=0 WD33C93 unimplemented/unknown command 03 scsi_send_data() without direction! - Bootable HDF with AMAX0 partition - WinUAE configs, one 68000 the other 68030/MMU - Extended ADF disk images for A-Max format Mac System 6.0.8 800K disks hxxp://www.4!s!h!a!r!e!d.com/file/uDRcWUtDce/A-Max_GVPtar.html [Change hxxp to http and remove ! from URL.] Boot HDF, double-click A-Max Startup icon on Workbench. Click Hard Disk / SCSI Preferences. Check Mount next to AMAX0, then OK and Start A-Max II. If you use the 68030 config, A-Max tries to use the MMU but that doesn't work correctly. Maybe an MMU emulation bug? On starting emulation, get red screen with this log output: Code:
68030 MMU enabled. Page size = 8192 Illegal instruction: 05bc at 0080005A -> 00F80AD2 Illegal instruction: 05bc at 0080005A -> 00F80AD2 Illegal instruction: 05bc at 0080005A -> 00F80AD2 ... |
![]() |
![]() |
#2 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
[moved from beta thread, mostly old WD33C93 emulation problems and similar stuff]
Quote:
But it still does not boot (HDF is not bootable? I set HDF as bootable to get the SCSI error, didn't try adfs). I don't see any SCSI emulation problems, also it does not repeat the command anymore, it stops after first SCSI READ(6) command. Quote:
I am not sure if this is worth the trouble yet.. EDIT: Biggest issue is 68030 design, cache is between execution unit and MMU (Cache caches logical addresses), 68040+ has cache after MMU (caches physical addresses) MMU 68030 does emulate instruction cache (if more compatible set) but it is emulated like 68040, emulating it like 68030 would be much more complex because every cache access needs to go through MMU and you also need to have special handling for any prefetch MMU access faults, they only must trigger if prefetched data is actually needed by execution unit. EDIT2: Fake very simple single-word prefetch emulation added that fetches and stores next opcode word only when MMU state changes. AMAX works now. Last edited by Toni Wilen; 03 January 2015 at 12:28. |
||
![]() |
![]() |
#3 | |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Quote:
With the latest winuae.exe the Mac sees the HD partition and offers to initialise it. I'm running the 6.0.8 installer now (using a 68000 config, will test 68030 later). About the 68030 MMU issue... reminds me of the way a soft reboot is done by RESET / JMP (An), with the prefetch having fetched the JMP opcode before memory goes away. I'll test A-Max with 68040 too, maybe it will work correctly there. Edit: Installing the OS seemed to work fine. After shutting down the emulated Mac and restarting A-Max, booting from the HD partition starts then I get a "sad Mac" icon with 0F0003 underneath it. That happens with both 68000 and 68030. Not sure what the problem is. Maybe because I selected to install a system for any Macintosh as opposed to a specific model? Or maybe another WD SCSI bug? Edit 2: Uploaded HDF after installing System 6.0.8 to hxxp://www.4!s!h!a!r!e!d.com/file/q71ytii2ba/GVP_A-Max_hardfile_installedSy.html Last edited by mark_k; 03 January 2015 at 14:17. |
|
![]() |
![]() |
#4 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Quote:
|
||
![]() |
![]() |
#5 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Stranger and stranger... I tested the HDF (with installed System 6.0.8 in AMAX0 partition) with A2091 instead of GVP, config attached. Can load A-Max, it automatically uses scsi.amhd. However on starting the Mac emulation I get a blue screen. There were no WD-related log messages after clicking Start A-Max.
|
![]() |
![]() |
#6 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
It seems to think SCSI is A3000 built-in and hangs while waiting for A3000 WD to respond.
|
![]() |
![]() |
#7 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
I also tested the HDF with the Oktagon driver (copy oktagon.amhd from the Oktagon disk to DEVS: before running A-Max). With that, clicking Start A-Max II then OK seems to do nothing at all; can still move mouse pointer, no WD log output obviously since the Oktagon doesn't use a WD SCSI chip. However after a while the emulated machine locks up with this log output:
Code:
step ignored drive 0, 125 step ignored drive 0, 100 A-Trap A873 at 632E2004 -> 74696E67 Exception 3 (632e2006) at 632e2004 -> 28003f! CPU halted: reason = 2 Last edited by mark_k; 03 January 2015 at 19:28. |
![]() |
![]() |
#8 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
EDIT: and same with my A3000 config too. (Your A3000 config have A2091? Why?) |
|
![]() |
![]() |
#9 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
I forgot to deselect the A2091 ROM in the A3000 config. After doing that it does boot to the sad Mac icon.
Still not sure what the issue with the Oktagon config is; I just tried again with the same result as before. Is it worth my trying to use the WinUAE debugger to get some kind of backtrace when it crashes/hangs. |
![]() |
![]() |
#10 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
|
|
![]() |
![]() |
#11 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Could be an incompletely cracked version? I'm trying again with (what I assume is) uncracked A-Max 2.53 and A-Max cartridge emulation (amax_rom_file= entry in config file). In the HDF I uploaded, v2.53 uncracked is in the A-Max II drawer.
[It might be a good idea to document that amaxromfile should be amax_rom_file in config files; it's not mentioned in winuaechangelog.txt...] I can't get A-Max to start booting the Mac OS (it gets to the initial screen with ? floppy disk icon). It seems there's some interaction between A-Max cartridge emulation and floppy drives. Boot the HDF with an A-Max hardware config (attached here). Notice that the DF0:???? icon on Workbench even though no disk is in the drive. If you insert an Amiga-formatted disk in DF0:, you need to DiskChange DF0: in order for the system to detect it, and similarly after ejecting. It seems disk changes not being detected affects A-Max too; it doesn't sense when an A-Max formatted disk is inserted, so can't boot. I tested WinUAE 1.4.5, the first release with A-Max cartridge emulation and the problem was there too. Not sure why I didn't notice that at the time... ![]() By the way, with logging enabled there are a huge number of lines like disk write DMA started, drvmask=0 motormask=0 as A-Max reads the Mac ROM data. |
![]() |
![]() |
#12 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
NTSC + Oktagon weird behavior seems to be gone when using original version. EDIT: "disk write DMA.." message is logged because amax starts disk DMA write without any (real) drive selected. Amax uses it to increase ROM address counter by one. Last edited by Toni Wilen; 04 January 2015 at 22:19. |
|
![]() |
![]() |
#13 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
About scsi.amhd not working with A590/A2091...
This is the routine that scsi.amhd uses to detect the SCSI type; none, A3000 or A590/A2091. (scsi.amhd from AMAX256.DMS which is a cracked version.) It looks a little strange. For A590/A2091, scsi.device has to not be in the system resident tag list for the check to work correctly. (Could the way A-Max resets into the Mac emulation cause the A590/A2091 ROM to not be initialised???) Call FindResident("scsi.device"). If found, assume we're running on an A3000. Set SCSI_type to $FF. Next is a check for the WD3393 base address. It uses either $DD2020 or $DD0041, depending on whether or not bits [7:5] of $DD203A.B are 101. Were different base addresses used in different A3000 revisions? Or could that be a chip type check (3393 vs 33C93A etc.)? It sets SCSI_type to 1 if using $DD2020 as base address. Code:
lbC0000B6 LEA (SDHD,PC),A5 MOVE.L A3,(lbL00001C-SDHD,A5) MOVEA.L (4).W,A6 LEA (ScsiName,PC),A1 JSR (_LVOFindResident,A6) TST.L D0 SNE (SCSI_type-SDHD,A5) BEQ.B .NotA3000 LEA ($DD2020).L,A0 ;Possible WD3393 base address MOVE.B ($1A,A0),D0 ;$DD203A ANDI.B #%11100000,D0 CMPI.B #%10100000,D0 BNE.B lbC0000F2 MOVE.W #$FFFF,(lbW00008C-SDHD,A5) NEG.B (SCSI_type-SDHD,A5) BRA.B lbC000138 lbC0000F2 MOVEA.L #$DD0041,A0 ;WD3393 base address to use BRA.B lbC000138 .NotA3000 LEA (ExpansionName,PC),A1 MOVEQ #0,D0 JSR (_LVOOpenLibrary,A6) MOVEA.L D0,A6 SUBA.L A0,A0 lbC000108 MOVEQ #0,D0 MOVE.W (CBM_WestChester_mfr_ID-SDHD,A5),D0 ;$202 MOVEQ #2,D1 ;A590/A2091 JSR (_LVOFindConfigDev,A6) TST.L D0 BNE.B .Found MOVEQ #0,D0 MOVE.W (CBM_WestChester_mfr_ID-SDHD,A5),D0 MOVEQ #3,D1 ;A590/A2091 SUBA.L A0,A0 JSR (_LVOFindConfigDev,A6) TST.L D0 BEQ.B .NoSCSI .Found MOVEA.L D0,A0 DBRA D7,lbC000108 ;??? MOVEA.L (cd_BoardAddr,A0),A0 ADDA.W #$91,A0 lbC000138 MOVE.L A0,(WD3393base???-SDHD,A5) MOVEQ #0,D0 RTS .NoSCSI MOVEQ #-$50,D0 RTS |
![]() |
![]() |
#14 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Quote:
Unless there was some different prototype A3000s or something. |
||
![]() |
![]() |
#15 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Ah, so with A500/2000 Kickstart 2.04 or earlier scsi.amhd should work correctly with A590/A2091.
I've attached a patched scsi.amhd which skips the A3000 check (so it won't for HDs connected to the A3000 SCSI controller). With that I can get the Mac OS to start booting from HD with A2091. But it gets stuck/hangs at the same point as the other SCSI controller types. |
![]() |
![]() |
#16 | |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Another curious thing about A-Max, which might relate to the recent 1mchipjumper option.
The A-Max 1.0 manual mentions a modification to allow use of 1MB contiguous memory for the emulated Mac. This was in the pre-ECS days. With the mod, the address of $C00000 RAM is moved to $080000. But then Kickstart thinks you have 1MB chip RAM (with OCS Agnus you don't), so ReadySoft provided a "KillChip" program to handle that. Does the current 1mchipjumper option apply only when ECS Agnus is used? Quote:
|
|
![]() |
![]() |
#17 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Quote:
Jumps to address 60c8 in following weird data: Code:
00006000 02AA 660E 2003 0680 0000 0080 A122 A023 ..f. ........".# 00006010 60E0 2050 91C0 D0FC 0080 A057 60D4 4E75 `. P.......W`.Nu 00006020 A920 3139 3833 2C20 3139 3834 2C20 3139 . 1983, 1984, 19 00006030 3835 2C20 3139 3836 2C20 3139 3837 2C20 85, 1986, 1987, 00006040 3139 3838 2C20 3139 3839 2C20 3139 3930 1988, 1989, 1990 00006050 2041 7070 6C65 2043 6F6D 7075 7465 7220 Apple Computer 00006060 496E 632E 0D41 6C6C 2052 6967 6874 7320 Inc..All Rights 00006070 5265 7365 7276 6564 2E0D 0D48 656C 7021 Reserved...Help! 00006080 2048 656C 7021 2057 65D5 7265 2062 6569 Help! We.re bei 00006090 6E67 2068 656C 6420 7072 6973 6F6E 6572 ng held prisoner 000060A0 2069 6E20 6120 7379 7374 656D 2073 6F66 in a system sof 000060B0 7477 6172 6520 6661 6374 6F72 7921 0D00 tware factory!.. 000060C0 8A00 0012 0000 0080 000A 8001 8001 7FFF ................ 000060D0 7FFF 8000 0012 0000 0094 000A 0000 0000 ................ 000060E0 0200 0280 8000 0436 0000 0088 FFFF FFFF .......6........ 000060F0 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF ................ 00006100 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF ................ 00006110 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF ................ |
||
![]() |
![]() |
#18 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,349
|
Since it seems like all .amhd drivers (well GVP, A2091 and Oktagon anyway) have the same problem... I wonder if there could be some timing issue/bug with the Mac OS and/or A-Max, which causes a problem if the hard drive is too fast.
If I boot from floppy, I can access the HD partition with no problems (as far as I can tell); it's just booting that breaks. |
![]() |
![]() |
#19 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Does Amax have any ide driver(s)? |
|
![]() |
![]() |
#20 |
Phone Homer
Join Date: Jun 2006
Location: 5150
Posts: 5,816
|
Sorry to but in -Still intrested in the old Amax - especially the 2.x versions that work on 68000
Ive got a little confused did you guys get in Working? as far as I know there are no AMHD IDE drivers - Well none that would work on my A600 ![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE Amax and .amhd | Gilloo | request.Apps | 3 | 15 July 2014 05:35 |
Wtb Amax 2,5 | bigmac | MarketPlace | 0 | 23 March 2010 15:11 |
Personal project: EEEPC, Gamebase and WINAUE: problems problems | butter100fly | project.GameBase Amiga | 15 | 09 August 2009 10:51 |
AMAX 2.5 File Transfer 2.5? | Amiga-emuman | request.Apps | 10 | 23 August 2006 07:57 |
GUI refresh problems + OpenGL Speed Problems in 0.821r4 | Danny Bacon | support.WinUAE | 1 | 07 June 2002 18:57 |
|
|