WinUAE 3.2.0 beta series

[oissery77]

Originally Posted by Toni Wilen

Either it is really corrupted or oktagon driver accepts bad checksums or something even weird.

My guess corruption due to bug in driveinit, also for some reason RDB driveinit block is still set even after you used driveinit command to remove the driver from RDB..

http://www.winuae.net/files/b/winuae.7z dumps whole block contents to log if checksum error. Perhaps it helps to see the real issue.

I tell you something wrong yesterday the command:
driveinit scsi.device 0
failed (same issue on real hardware with the broken RDB).
The log of driveinit on shell says :
"Reading RDB block on scsi.device unit 0 failed!
done!"

I had read too quickly the "done" word.

Here is the winuae.txt with the version that dumps whole block, done in UAE mode for Hard Drive.

[Toni Wilen]

Originally Posted by B14ck W01f

In the last stable release, I was able to install Amiga Unix 2.1 using the exact config I attached below. However, everything changed since Beta 7 onwards. The installation whinges about two missing files on the tape, then aborts. This occurs no matter how many fresh copies of your tape I used.

Could you create new log with -scsilog -scsiemulog command line parameters?

[B14ck W01f]

Originally Posted by Toni Wilen

Could you create new log with -scsilog -scsiemulog command line parameters?

Is this what you are looking for?

https://www.dropbox.com/s/ec4h28invd...07%29.txt?dl=0

[Toni Wilen]

Originally Posted by B14ck W01f

In the last stable release, I was able to install Amiga Unix 2.1 using the exact config I attached below. However, everything changed since Beta 7 onwards. The installation whinges about two missing files on the tape, then aborts. This occurs no matter how many fresh copies of your tape I used.

Does http://www.winuae.net/files/b/winuae.7z fix it?

[ero__]

Originally Posted by Toni Wilen

- 2G of Amiga address space available (vs ~1G to ~1.5G in 32-bit version under 64-bit OS). Because JIT still requires Amiga address space inside first 4G of host process address space and Windows allocates few pages in the middle of first 4G, 2G is the current max. Technically this is not a problem because AmigaOS is not really designed to support RAM at 2G-4G of address space, programs may use signed pointers and some exec functions use address bit 31 for error state. (In theory 3G may be possible later if it is really needed)
- Use "UAE" RAM allocation mode (not "Real") if you want max available Z3 RAM (up to 1.5G. Z3 RAM + RTG VRAM + 256M must be less than or equal to 2G. Anything more = crash.
- 64-bit JIT FPU is not fully functional yet. Do not enable.

Does this for OS 3.9?

[B14ck W01f]

Originally Posted by Toni Wilen

Does http://www.winuae.net/files/b/winuae.7z fix it?

Yes.

[Toni Wilen]

Originally Posted by ero__

Does this for OS 3.9?

Yes. OS 3.x is the default if nothing else is mentioned

Originally Posted by oissery77

Here is the winuae.txt with the version that dumps whole block, done in UAE mode for Hard Drive.

Retry with next beta, it didn't log all required errors.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3200b14.7z
http://www.winuae.net/files/b/winuae64_3200b14.7z

Beta 14:

- 64-bit JIT fixes. JIT FPU also fixed. (Frode)
- RDB parser dumps block contents to the log if parsing fails.
- SCSI tape request sense tape position bits (end/beginning) was not reported correctly (b7)
- UAE devices (uaeserial, uaescsi and so on) are now supported under KS 1.2.
- Directory harddrives and uaehf.device is now KS 1.2 automount/boot capable.

KS 1.2 boot notes:
- Logic reverse engineered from Multi Evolution SCSI driver.
- First drive in Harddrives panel is boot drive, even if it has lower boot priority than other drives.
- If boot priority = -128 (no autoboot): don't enable fake DF0: boot disk hack.
- Ugly hack. Temporarily patches DoIO() to inject fake df0: boot block and PutMsg() to get control after dos has been initialized.

[oissery77]

Originally Posted by Toni Wilen

Retry with next beta, it didn't log all required errors.

ok Toni, log is in attachment.

[rbm]

All recent releases do not read correctly the JIT settings configuration.

Always show "indirect" when loaded even though "direct" is set and saved.

Please fix !

[Toni Wilen]

Originally Posted by rbm

All recent releases do not read correctly the JIT settings configuration.

Always show "indirect" when loaded even though "direct" is set and saved.

Please fix !

Works for me. It rarely is that simple = config is always needed! Also check log.
EDIT: also last working version missing!

[rbm]

Originally Posted by Toni Wilen

Works for me. It rarely is that simple = config is always needed! Also check log.
EDIT: also last working version missing!

OK. Works fine for a new configurations, but not for the old saved.
Configured again from scratch and works fine.

Thanks !

[Arnie]

SRAM as disk or ram stopped working in b14 with jit enabled.

As disk:
Always a crc error at the end of the disk, whether 2mb or 4mb.

As Ram:
Fails to boot from Sram most times, sometimes a HALT3 error. (always tries to boot from Sram first)

Config and logs, Sram files (prepared as disk & ram) attached.

All Jit enabled configs give same results. (All work in beta 13, HD boots first)

[Toni Wilen]

Originally Posted by rbm

OK. Works fine for a new configurations, but not for the old saved.
Configured again from scratch and works fine.

If this behavior really changed in betas, it would be nice to know which beta changed it.

Originally Posted by Arnie

SRAM as disk or ram stopped working in b14 with jit enabled.

Does http://www.winuae.net/files/b/winuae.7z fix it?

Originally Posted by oissery77

ok Toni, log is in attachment.

Logging still had bugs (wrong block shown..), yet another log needed using above winuae.7z. Sorry..

[Arnie]

Originally Posted by Toni Wilen

Does http://www.winuae.net/files/b/winuae.7z fix it?

Yes, fixed

[oissery77]

Originally Posted by Toni Wilen

Logging still had bugs (wrong block shown..), yet another log needed using above winuae.7z. Sorry..

Sure, new log in attachment.

[Toni Wilen]

Originally Posted by oissery77

Sure, new log in attachment.

Unfortunately RDB is corrupted.

Partition block pointer in RDSK block points to LSEG (filesystem) block, it should point to PART block.

[oissery77]

Originally Posted by Toni Wilen

Unfortunately RDB is corrupted.

Partition block pointer in RDSK block points to LSEG (filesystem) block, it should point to PART block.

ok Thanks Toni, i will format the CF soon and try to use this oktapussy patch on the real hardware to hope bypass my 2GB limit partition.

[rbm]

Originally Posted by Toni Wilen

Works for me. It rarely is that simple = config is always needed! Also check log.
EDIT: also last working version missing!

The JIT "direct/indirect" "save/load" configuration works while is not selected any accelerator board.

When JIT "direct" is selected together any acceletaror board, and the configuration saved, the JIT settings always show "indirect" when the configuration is loaded.

And needs to be set again to "direct" each time when something is changed.

[FrodeSolheim]

Originally Posted by rbm

When JIT "direct" is selected together any acceletaror board, and the configuration saved, the JIT settings always show "indirect" when the configuration is loaded.

It sounds like the problem I fixed in commit https://github.com/tonioni/WinUAE/co...07f92b111e30c6 (at least if "any" = "some"), so it should work fine again in the next beta version