WinUAE 3.0.0 beta series (was 2.8.2/2.9.0)

[thomas]

Originally Posted by Toni Wilen

CSPPC only? All boards have slightly different SCSI IO and most have very different SCSI chips. (wd33c93/53c90/53c710/53c770)

I tried all boards with 060. They all crash. Except Warp Engine. But I don't know what a Warp Engine is. Does it even have SCSI?


BTW, if I select SCSI (auto) on the Harddrives page (with a CSPPC), it does not mount the HDD. Seems like Accelerator SCSI is not included in SCSI (auto).

[huepper]

Originally Posted by thomas

I tried all boards with 060. They all crash. Except Warp Engine. But I don't know what a Warp Engine is. Does it even have SCSI?
...

Please have a look: http://amiga.resource.cx/exp/warpengine
It comes with a NCR 53C710 @ 40 MHz.

[Mad-Matt]

Interestingly it did used to crash for me as well, but in Beta12, it seems ok. I have also deleted and remade some of my highend configs as well so maybe an erent setting that was in my old configs was crashing the emulated scsi (not just accelerator scsi) to crash when accessing. The bug that caused it to corrupt the hardfile on writing was fixed.

Not a helpful post I know, but All I can say is that I can now use the various scsi modes without fault.

[thomas]

Originally Posted by Mad-Matt

I have also deleted and remade some of my highend configs as well so maybe an erent setting that was in my old configs was crashing the emulated scsi (not just accelerator scsi) to crash when accessing.

The config posted in #519 was made from scratch, starting with an A4000 quickstart.

[huepper]

Next bad news.
I changed back to b12 and try to add a hardfile created with b13.
Then a new window popps up. (picture)
If i click OK on this window, WinUAE crashes without dump file.

This are the details of the program error:

Problemsignatur:
  Problemereignisname:    BEX
  Anwendungsname:    winuae.exe
  Anwendungsversion:    2.9.0.0
  Anwendungszeitstempel:    53f0e19d
  Fehlermodulname:    winuae.exe
  Fehlermodulversion:    2.9.0.0
  Fehlermodulzeitstempel:    53f0e19d
  Ausnahmeoffset:    0080965b
  Ausnahmecode:    c0000409
  Ausnahmedaten:    00000007
  Betriebsystemversion:    6.3.9600.2.0.0.768.101
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    a0e5
  Zusatzinformation 2:    a0e5f4cba3a69cbdb5ae4f66daaafe2d
  Zusatzinformation 3:    17ba
  Zusatzinformation 4:    17ba775807e68c759e86552722984d9f

[Toni Wilen]

Originally Posted by huepper

Next bad news.
I changed back to b12 and try to add a hardfile created with b13.
Then a new window popps up. (picture)
If i click OK on this window, WinUAE crashes without dump file.

Problem found. VHD hardfiles created with b12 have wrong disk type id, they need to be created again.

EDIT: and because hdf type variable is not properly cleared if vhd validation fails, old version still accept it..

[huepper]

Ok, thanks for the information.
HDF files seems to be ok, tested.

[Toni Wilen]

Originally Posted by thomas

I tried all boards with 060. They all crash. Except Warp Engine. But I don't know what a Warp Engine is. Does it even have SCSI?

Warp Engine and A4091 uses same chip. CyberStorm uses newer NCR chip version but DMA part is still the same. Weird if A4091 also works..

Attach log with scsi emulation logging enabled: "winuae -log -scsilog -scsiemulog -logflush"

My guess is that there is some longer transfer that overflows some buffer or something..

BTW, if I select SCSI (auto) on the Harddrives page (with a CSPPC), it does not mount the HDD. Seems like Accelerator SCSI is not included in SCSI (auto).

Yeah, I haven't bothered with this yet..

[thomas]

Originally Posted by Toni Wilen

Attach log with scsi emulation logging enabled: "winuae -log -scsilog -scsiemulog -logflush"

I'm on a different PC now, so it's a slightly different environment. Therefore I attach all data again.

[Toni Wilen]

Originally Posted by thomas

I'm on a different PC now, so it's a slightly different environment. Therefore I attach all data again.

Download http://www.winuae.net/files/b/winuae.zip and attach log again. Use same command line parameters, no need to attach dump. I forgot that -scsiemulog only logged CD scsi emulation, not HD.

[Retrofan]

Thomas I don't know if things have changed (I want to know), but before you coudn't use in RAM "Autoconfig Z2 Fast Ram" or "Jit Direct Z3" with a CyberstormPPC.

[Toni Wilen]

Originally Posted by Retrofan

Thomas I don't know if things have changed (I want to know), but before you coudn't use in RAM "Autoconfig Z2 Fast Ram" or "Jit Direct Z3" with a CyberstormPPC.

Z2 autoconfig has nothing to do with this and JIT Direct Z3 depends on other things, like JIT being on and it is off (EDIT: and it does not matter if you run m68k AOS)

Dump shows "real" crash but it does not tell why it happens, except that there is some overflow/corruption somewhere.

[thomas]

Originally Posted by Toni Wilen

Download http://www.winuae.net/files/b/winuae.zip and attach log again. Use same command line parameters, no need to attach dump. I forgot that -scsiemulog only logged CD scsi emulation, not HD.

Done.

[Toni Wilen]

Originally Posted by thomas

Done.

Thanks. It is "too long" transfer, 910 blocks which overflows internal buffer. Unfortunately SCSI emulation needs separate buffer but allocating megabytes just for SCSI buffers isn't that optimal. Need to find some better solution..

SCSIEMU HD 0: 28.00.00.05.AB.B0.00.03.8E.00.00.00

[AMIGASYSTEM]

Then Toni, I set hardfile "IDE", set cyberstormppc_44.71.rom, tried all the settings on the forum and the results do not change; Blue screen first, then screen bands are colorful and finally screen Pink.

I tried to use the Kikstart 3.1 A4.000 and I get a strange message "can not find system", attach 2 of 2 winuae_debug Kikstart

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Then Toni, I set hardfile "IDE", set cyberstormppc_44.71.rom, tried all the settings on the forum and the results do not change; Blue screen first, then screen bands are colorful and finally screen Pink.

I tried to use the Kikstart 3.1 A4.000 and I get a strange message "can not find system", attach 2 of 2 winuae_debug Kikstart

You still have CD mounted as "UAE". (uaescsi.device and/or CDFS mount option in harddrives panel configured).

[AMIGASYSTEM]

Originally Posted by Toni Wilen

You still have CD mounted as "UAE". (uaescsi.device and/or CDFS mount option in harddrives panel configured).

Sorry Toni, the translation does not help me, it may be of interest:
Off "automount CDFS CD / DVD" the CD is not mounted!, Replaced with cyberstormppc_44.67.rom cyberstormppc_44.69.rom, now also works A4000 Kickstart 3.1 and the installation CD is successful without ""CDFS Automount CD/DVD Drives"", but when I start I always screen Blue screen Pink colored bands and infinity. I attach the log and I hope not to bother!.

[AMIGASYSTEM]

Finally I was able to boot OS 4, I copied "manually" by OS4 Classic Dopus4 directly from CD to OS4 Classic, Hardfile configured as IDE, I removed the check mark for "uaescsi.device" from "Miscellaneous Expansion", practically the tick should be removed every time you start please is stored.

[BinoX]

Originally Posted by AMIGASYSTEM

I removed the check mark for "uaescsi.device" from "Miscellaneous Expansion", practically the tick should be removed every time you start please is stored.

I have added this step to my tutorial and credited you in the update section of the first post. I've never noticed that option in that section before, many thanks for pointing it out.

[mark_k]

Originally Posted by Toni Wilen

Thanks. It is "too long" transfer, 910 blocks which overflows internal buffer. Unfortunately SCSI emulation needs separate buffer but allocating megabytes just for SCSI buffers isn't that optimal. Need to find some better solution..

If I remember correctly, ShapeShifter (Mac emulator) has a similar issue. If the emulated Mac attempts a transfer larger than the current buffer size, it frees the current buffer and tries to allocate one twice as large. Maybe a similar approach could be used for WinUAE?