WinUAE 3.5.0 beta series (was 3.4.1)

[mark_k]

Yep, the .scp file is completely broken; just doing Dir in a CLI gives a disk error requester. The DMS might be OK; at least all files on it copy without errors.

[shaf]

The DMS file is OK, That's the source I used to update the Installer, I'll recreate the SCP image.

[DamienD]

Originally Posted by shaf

The DMS file is OK, That's the source I used to update the Installer, I'll recreate the SCP image.

Why not just upload the .DMS file?

I'm sure Toni knows how to handle this

[shaf]

I did upload the DMS image, the SCP file contains a newer Hard Drive Table

[Toni Wilen]

DMS works (emulation is nearly done) but it seems it does not have A1000 kickdisk install support.

[mark_k]

After quickly looking at the Comspec SetClock program and ComspecSCSI.device...

The SA1000 can have an optional real-time clock. The SetClock program expects bit 0 of er_SerialNumber (in the ExpansionRom structure) to be zero for RTC to be present.

ComspecSCSI.device command numbers 12 and 13 respectively are used to read and set the RTC time . (Those command numbers are TD_REMOVE and TD_CHANGENUM for "normal" trackdisk-like devices... but probably ComspecSCSI.device isn't supposed to be trackdisk-like, that job is for ComspecHD.device?)

Hopefully the pattern of register accesses could allow you to figure out which type of RTC chip it uses.

[Toni Wilen]

Not going to happen without knowing type of the chip in advance. Clocks are too boring.

[mark_k]

shaf mentioned having the schematic and memory map…

Failing that I'll try to figure it out.

[shaf]

The Clock Chip is OKI 6242B. I/O Space and ROM Space sit in Expansion Space ($E8000) and Cartridge Space ($F00000). The SCSI chip is WD33C93.

IF you require it I will scan the Schematic and Memory Map But they are very old copies.

Shaf

[mark_k]

They could still be useful for emulation, also maybe to someone with the real hardware, if they want to repair their unit. So please do upload them!

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3410b7.7z
http://www.winuae.net/files/b/winuae64_3410b7.7z

Beta 7:

- Accessing accelerator board SCSI IO region without any added SCSI device caused crash.
- winlaunch.lib native code use attempts are now internally "emulated". Library is not used or needed anymore.
- Old style 0xf00000 boot rom is automatically mapped (if memory is not already in use and "new" rom mode) if it looks like program is directly jumping to boot rom trap space instead of using uae.resource.
- AGA FMODE>0 unaligned bitplane and sprite pointer behavior should be now accurately emulated. (It is not simple masking). Sprites not tested (too boring) but both should use same DMA hardware. [I saw some comments somewhere, I'd recommend contacting me for faster response ]
- Added A590 v4.6 boot ROM to ROM scanner.
- Fixed A590 XT mode request sense handling (for example if out of bounds read).
- 68040/060 without FPU or 68060 with FPU disabled exception had wrong PC OF FAULTED INSTRUCTION field in exception stack frame.
- Comspec SA-1000 controller emulation remaining features implemented.

[NorthWay]

Is that Comspec controller the one that Dragon's Lair supported?

[mark_k]

The Comspec SA1000 RTC registers are at even bytes starting at board offset $80A0.

[Toni Wilen]

Comspec RTC emulation and enable/disable option added. Uses already existing MSM emulation = writing to clock registers (except config registers) are not supported. Current date is always returned.

Boot disk returns "Date is unreadable" so either something is wrong or it does not like >=2000 dates (which is more likely..).

[mark_k]

How do you emulate >=2000 years in the MSM6242B? ComspecSCSI.device seems to treat year <78 as meaning 2000+year. In other words, for 2017 you'd need to have 17 in the year registers. So 7 in 1-year digit register, 1 in 10-year digit register. And it requires 10×(10-year reg) + (1-year reg) be <= 99.

cf. this in the 2.5.0b20 changelog entry:

- RTC year value is saved differently depending on OS version, Pre-2.0: RTC year value = current year - 1900,
  2.0+: year value = last 2 digits. Both methods supported when reading. WinUAE now uses pre-2.0 method if
  MSM clock chip (because this is the only type that KS1.x supports), 2.0+ if RF clock chip, previously always used -1900 method.

[Toni Wilen]

Originally Posted by mark_k

How do you emulate >=2000 years in the MSM6242B? ComspecSCSI.device seems to treat year <78 as meaning 2000+year. In other words, for 2017 you'd need to have 17 in the year registers. So 7 in 1-year digit register, 1 in 10-year digit register. And it requires 10×(10-year reg) + (1-year reg) be <= 99.

It uses invalid BCD values (2017 = 117 = B7), this is more AmigaOS compatible.

Surprisingly Comspec accepts the date (and it even is printed correctly) if year value is 17 (instead of 117). So Comspec now uses different method.

[mark_k]

Also, the function in ComspecSCSI.device to set the RTC always sets the 24/12 bit (i.e. 24-hour mode) in control register F.

[mark_k]

Originally Posted by shaf

IF you require it I will scan the Schematic and Memory Map But they are very old copies.

Do you have a user manual too? I've been reverse-engineering ComspecSCSI.device out of curiosity, but maybe I'm wasting my time if its command set is already documented in the manual.

[mark_k]

Some more info about the Comspec RTC. Not sure whether you already emulate this, but bit 0 of the write-only register at board offset $8080 seems to be an enable for the RTC. The RTC probably only appears on the bus when that bit is set.

The ComspecSCSI.device commands for both reading and setting the RTC set that bit before accessing the RTC, and clear it afterwards. I guess protecting the RTC that way reduces the likelihood of a crashing program affecting the stored time/date.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3410b8.7z
http://www.winuae.net/files/b/winuae64_3410b8.7z

Beta 8:

- Blitter BDAT register's old content was not preserved and shifted in when BDAT was rewritten with CPU or copper and current B-shift was non-zero. (Probably never used by purpose but emulation still should be always correct)
- 68010+ RTE didn't generate format error exception if frame was not supported by selected CPU but it was supported by other 680x0 model and CPU emulation mode was not MMU or more compatible.
- Added Comspec SA-1000 RTC emulation. Always returns current host time, time registers are not writable.
- Built-in HRTMon 2.37 update.
- Added two A2088T BIOS 4.0 (390657-01) ROM versions with different internal date (09/11/89 and 14/11/89).
- Added A2386SX 1.00.03 ROM.
- PC bridgeboard NE2000 boot crash fix. (Introduced when NIC specific MAC setting was added)
- Adjusted windowed mode mouse clipping so that when winuae window is partially under taskbar (including auto hide taskbar or partially outside of monitor, Amiga mouse won't randomly hit hidden borders (if Windows Mouse mode) or become unexpectedly uncaptured (any mode, window partially under taskbar).
- Do not delay SCSI/ATAPI emulation audio CD play state change from startup to playing. Only CD32/CDTV require it.