WinUAE 3.1.0 beta series

[supaduper]

Excellent work Toni, donated !

[Snake79]

Getting crash with latest beta8 when trying to load A4000 AOS41FE config (i have created new QS config also). Older versions are working fine...

[Toni Wilen]

Originally Posted by supaduper

Excellent work Toni, donated !

Thanks

Originally Posted by Snake79

Getting crash with latest beta8 when trying to load A4000 AOS41FE config (i have created new QS config also). Older versions are working fine...

Does http://www.winuae.net/files/b/winuae.zip fix it? (Too stupid bug, it accidentally worked without full optimizations enabled..)

[Snake79]

Yeah. It is working now. Great!

[waldiamiga]

Thanks for Fix.

[Snake79]

Toni, sorry to bother, but i have problem with another config (A1200 040, WB3.x). When i load and run it, i have endless black screen (CPU 10%, FPS 50) and nothing happens (b8 and fixed b8). Can't even go to Early Startup Boot Options... Last working beta was b7 and older.

[Snake79]

Maybe its because emulator on that config forces ROM / Accelerator Board SCSI and Blizzard 1240/1260 ROM (32k)? On previous it was A590/A2091?...

[Toni Wilen]

Should be fixed now (same url). (Reporting bugs is not a bother to anyone, it is what this thread is designed to do)

SCSI Kit was always enabled even when ROM was not selected. HD selected as IDE was (also) mounted as SCSI if accelerator has SCSI.

[Snake79]

FIXED as you said! Thanks.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3100b9.zip

Beta 9:

- Fixed harddrive config parse crash. (b8)
- Blizzard SCSI Kit was always enabled if compatible accelerator board was selected. (b8)
- Accelerator board with SCSI and "IDE (auto)": HD was mounted as accelerator SCSI. (b8)
- Accelerator board ROM selection is not anymore in SCSI/Boot ROM list.
- Added autoboot disabled jumper option to harddrive controllers. Not all devices supported yet. (Some only hardware disable rom chip, some change autoconfig data in hardware level)

[mark_k]

Originally Posted by Toni Wilen

SupraDrive 500XP:

- v3.8 ROM (AMAB6) added. (Anyone have AMAB5 or older? I'd like to know why older versions have so many compatibility problems with modern drives. A2000 WordSync version also accepted.)

You could try the BindDrivers-loadable version from the SupraBoot disk. The ones on amiga.resource.cx have two versions of the driver, dated 24-Jul-91 (3.0?) and 26-Nov-91 (3.8?).

Edit: And if you didn't already see it, "Docs/Read Me" on the SupraTools38b disk has some info about driver changes between 3.0 and 3.8.

[Toni Wilen]

Originally Posted by mark_k

You could try the BindDrivers-loadable version from the SupraBoot disk. The ones on amiga.resource.cx have two versions of the driver, dated 24-Jul-91 (3.0?) and 26-Nov-91 (3.8?).

Didn't notice anything interesting 3.0 vs 3.8 (3.0 = AMAB5?).

It is now confirmed that same ROM image supports SupraDrive 4x4, 500, 500XP and 2000 WordSync. 3.8 boot disk supraromchk detects correct hardware and reports valid ROM (Except with 4x4 which is non-autoboot)

(All 4 are now emulated, except 4x4's clock)

Edit: And if you didn't already see it, "Docs/Read Me" on the SupraTools38b disk has some info about driver changes between 3.0 and 3.8.

Unfortunately it does not mention anything interesting either.

[mark_k]

Testing 3.1.0b9, same crash with winuae.exe dated 2015-02-10 17:10.

Using an A500-like config with GVP Series I controller (its ROM marked as disabled), 50MB all-zero/blank hardfile connected as unit 0. Boot GVP-SeriesI_v1.3.dms, open disk icon then open install icon. Answer Y twice and WinUAE crashes. [I didn't bother attaching dump file because I'm using Wine.]

[Toni Wilen]

Originally Posted by mark_k

Testing 3.1.0b9, same crash with winuae.exe dated 2015-02-10 17:10.

Using an A500-like config with GVP Series I controller (its ROM marked as disabled), 50MB all-zero/blank hardfile connected as unit 0. Boot GVP-SeriesI_v1.3.dms, open disk icon then open install icon. Answer Y twice and WinUAE crashes. [I didn't bother attaching dump file because I'm using Wine.]

Fixed. Series I SRAM buffer was only allocated if ROM was enabled..

[mark_k]

Thanks, it gets further now, in fact installation seems to complete. I continued accepting the defaults and the installer created two 25MB partitions, formatted them and copied files to one. Then it created a boot floppy disk. After that it tells you to reboot with the boot floppy in DF0:. (Archive with HDF and boot floppy attached; remove .zip extension before unpacking it.)

[I think I forgot to enable RDB mode for the HDF in the config I attached above. You should do that before running the installer, if you want to run it yourself.]

On booting the boot floppy, its startup-sequence runs BindDrivers (which loads the driver, which automatically mounts the partitions) then transfers control to the HD. After a short while though the startup sequence is interrupted, saying SYS:gvpscripts/tstGVPscsi failed returncode 20

I'll look at the tstGVPscsi code to see what it might be doing. But the last SCSI lines in the log were:
-> DATAOUT=512 ST=0 SENSELEN=0 REPLYLEN=0
SCSIEMU HD 0: 08.00.68.C4.01.00.00.00.00.00.00.00 CMDLEN=6 DATA=067A0C18
-> DATAOUT=512 ST=0 SENSELEN=0 REPLYLEN=0
SCSIEMU HD 0: 08.00.68.C5.01.00.00.00.00.00.00.00 CMDLEN=6 DATA=067A0C18
-> DATAOUT=512 ST=0 SENSELEN=0 REPLYLEN=0
SCSIEMU HD 0: 1B.00.00.00.01.00.00.00.00.00.00.00 CMDLEN=6 DATA=067A0C18
-> DATAOUT=0 ST=0 SENSELEN=0 REPLYLEN=0
So it looks like it issues a START STOP UNIT command.

[Toni Wilen]

Originally Posted by mark_k

Thanks, it gets further now, in fact installation seems to complete. I continued accepting the defaults and the installer created two 25MB partitions, formatted them and copied files to one. Then it created a boot floppy disk. After that it tells you to reboot with the boot floppy in DF0:. (Archive with HDF and boot floppy attached; remove .zip extension before unpacking it.)

[I think I forgot to enable RDB mode for the HDF in the config I attached above. You should do that before running the installer, if you want to run it yourself.]

On booting the boot floppy, its startup-sequence runs BindDrivers (which loads the driver, which automatically mounts the partitions) then transfers control to the HD. After a short while though the startup sequence is interrupted, saying SYS:gvpscripts/tstGVPscsi failed returncode 20

I'll look at the tstGVPscsi code to see what it might be doing. But the last SCSI lines in the log were:
-> DATAOUT=512 ST=0 SENSELEN=0 REPLYLEN=0
SCSIEMU HD 0: 08.00.68.C4.01.00.00.00.00.00.00.00 CMDLEN=6 DATA=067A0C18
-> DATAOUT=512 ST=0 SENSELEN=0 REPLYLEN=0
SCSIEMU HD 0: 08.00.68.C5.01.00.00.00.00.00.00.00 CMDLEN=6 DATA=067A0C18
-> DATAOUT=512 ST=0 SENSELEN=0 REPLYLEN=0
SCSIEMU HD 0: 1B.00.00.00.01.00.00.00.00.00.00.00 CMDLEN=6 DATA=067A0C18
-> DATAOUT=0 ST=0 SENSELEN=0 REPLYLEN=0
So it looks like it issues a START STOP UNIT command.

I get same error without any START STOP UNIT commands (or any SCSI commands) when booting from installed HD (with enabled autoboot ROM).

START STOP UNIT is "supported", it always returns immediate success.

[mark_k]

Originally Posted by Toni Wilen

I get same error without any START STOP UNIT commands (or any SCSI commands) when booting from installed HD (with enabled autoboot ROM).

It won't work properly with a gvpscsi.device autoboot ROM, you need to use either no ROM or an old scsidev ROM. Even the BETA2 ROM is too new. (Only the old scsidev.device supports command 27 for issuing arbitrary SCSI commands.)

Edit: This is strange... I get that error with Kickstart 1.2 or 1.3. But with Kickstart 2.04 or 3.1, it boots to Workbench with no error.

The comment in DH0:gvpscripts/hdstartup-continue before the line which runs tstGVPscsi is: "Automount partitions on slower Hard Disks which may be connected (e.g. ST)." (ST being the first letters of Seagate drive models.)

[Toni Wilen]

Originally Posted by mark_k

It won't work properly with a gvpscsi.device autoboot ROM, you need to use either no ROM or an old scsidev ROM. Even the BETA2 ROM is too new. (Only the old scsidev.device supports command 27 for issuing arbitrary SCSI commands.)

Edit: This is strange... I get that error with Kickstart 1.2 or 1.3. But with Kickstart 2.04 or 3.1, it boots to Workbench with no error.

The comment in DH0:gvpscripts/hdstartup-continue before the line which runs tstGVPscsi is: "Automount partitions on slower Hard Disks which may be connected (e.g. ST)." (ST being the first letters of Seagate drive models.)

I can't see anything wrong with SCSI emulation. It must be something else.

[thomas]

Originally Posted by Toni Wilen

Beta 9:

1. CyberstormPPC quickstart crashes immediately after start unless you go to the ROM page and select the "Cyberstorm PPC (128k)" ROM. (see ppc_quickstart.zip)

2. select A4000/CS PPC quickstart, go to hard drives, add hardfile, change controller to the first "Accelerator Board" in the list, ok -> crash. (I didn't see that this is now divided into IDE and SCSI and the first Accel. Board is IDE. It works if I correctly select Accel. Board under SCSI.)
(see accel_ide.zip)

[guyfry]

Another Error on WinUAE v3.1 B9

"24-bit address space is not supported with selected accelerator board configuration". -> 68060 running + PPC!?

... only with HD-ACKS-ROMS.