WinUAE 1.4.3 public beta series

[BippyM]

What is the "High End WINUAE" in the rom scsn window?

[billy]

Originally Posted by Toni Wilen

- A3000 Quickstart settings added, 1.4 = KS with Kickstart menu, SuperKickstart disk (or HD installed SuperKickstart) required.

A3000 Quickstart w/:

• 3.1 ROM, 2MB Chip + 8MB Fast
• 1.4 ROM, 2MB Chip + 8MB Fast

= LOVE

[StevenJGore]

Thanks for another beta, Toni! Much appreciated.

The ROM scan report dialog, for me, reports that the following ROM's are unavailable:

- A500 Boot ROM 1.2
- A500 Boot ROM 1.3
- CDTV

But I have these ROM's, and WinUAE 1.4.2a has no problems detecting them. All I've done is replaced the 1.4.2a winuae.exe with the 1.4.3 Beta 3 winuae.exe. No other changes, the ROM path still points to the same place.

ROM rescan required. I will delete your so called bug report if you didn't rescan roms!

I tried rescanning several times, including after quitting and restarting WinUAE, but it doesn't appear to make any difference.

Any suggestions?

Steve.

[sink]

same problem here but if i rescan, all is oki with the last beta

[turrican3]

thanks for the good job toni
And for all is ok

[Carcenomy]

Originally Posted by Toni Wilen

This is quite useless report, sorry. "Other applications="? (ALWAYS LIST NAMES, no names = I will ignore it) Perhaps "too big" drive? (even 80MB can be too big with early HD software..) Perhaps it expected specific harddrive partition name. (for example A590 utilities expect DH0:, anything else = no drive detected)

PrepHD doesn't work at all. HDToolbox works, however although both drive definitions are for 20Mb drives, a 21Mb or larger HDF is required or WinUAE crashes (since HDToolbox is trying to access a cylinder past the end of the drive). FormatHD and InstallHD don't work if the drive is partitioned using HDToolbox default settings.

I tried installing Populous II, and no matter what, the emulation crashes on the spot and creates a dump file. I'll have a play with the new Beta and see how it goes.

[billy]

FYI -
After rescanning ROMs, Main ROM file: KS ROM v3.1 (A4000T) rev 40.70 (512k) accurately shows in 'System ROM Settings'. Though ROM scan shows = A4000: unavailable

A3000 Super Kickstart memory hack only works with KS 2.x on SuperKickstart-Disk v2.04 rev 37.175 (1991)(Commodore)(A3000).adf, not KS 1.3 of the same.

A3000 Super Kickstart memory hack does not work at all with SuperKickstart-Disk v2.0 rev 36.143 (1990)(Commodore)(A3000).adf

[Mclane]

Can anyone answer what differences if any are there to the Supercard IV with loader disc emulation in the new beta 3?

Is the loader actually needed / adds other options or is it just that the emulation is now 100% for the perfectionists here ie you can use the rom or to be exact boot the loader instead?

Just wondered?

[Mclane]

Originally Posted by bippym

What is the "High End WINUAE" in the rom scsn window?

I'd love to know too

"This is not a secret society, it's just a society with secrets"

[Toni Wilen]

Originally Posted by Mclane

is it just that the emulation is now 100% for the perfectionists here ie you can use the rom or to be exact boot the loader instead?

Yes. It is only for completeness.

What is the "High End WINUAE" in the rom scsn window?

It is nothing special, it is example/starting point configuration for most expanded configuration.

After rescanning ROMs, Main ROM file: KS ROM v3.1 (A4000T) rev 40.70 (512k) accurately shows in 'System ROM Settings'. Though ROM scan shows = A4000: unavailable

A4000 != A4000T. A4000T ROM has SCSI driver (that freezes without SCSI hardware) There is hack that disables the driver by patching KS but it will be removed when SCSI hardware emulation is implemented.

[Mclane]

Re the Super Iv emulation

Originally Posted by Toni Wilen

Yes. It is only for completeness.

Thanks for clearing that up..


Re the High end rom scan option.

Originally Posted by Toni Wilen

It is nothing special, it is example/starting point configuration for most expanded configuration.

I've seen the high end expanded configuration section in Configurations, just wondered why there was a similar named item in the Romscan window that says I'm missing I presume a rom.

Just wondered what the rom / image did that was special if anything?

Anyway, thanks for the answers Toni.....All work appreciated as always!

[Toni Wilen]

Originally Posted by Carcenomy

PrepHD doesn't work at all. HDToolbox works, however although both drive definitions are for 20Mb drives, a 21Mb or larger HDF is required or WinUAE crashes (since HDToolbox is trying to access a cylinder past the end of the drive). FormatHD and InstallHD don't work if the drive is partitioned using HDToolbox default settings.

I tried installing Populous II, and no matter what, the emulation crashes on the spot and creates a dump file. I'll have a play with the new Beta and see how it goes.

Crash = "out of bounds" error? (dialog and also in winuaelog.txt) It means your HDF was smaller than size specified in partition table (see below)

Problem is A590 install disk, HDToolbox that comes with A590 install disk only understands SCSI-1 INQUIRY format and SCSI emulation uses SCSI-2 which means "Read Configuration from Drive" fails to work. You need to manually adjust drive parameters until drive size is smaller than size of HDF.

I guess using SCSI-1-style inquiry response when using A590/A2091 should fix this problem without any side-effects.

"out of bounds" crash will be fixed soon.

[Toni Wilen]

- A3000 36.141 KS ROM SCSI driver compatiblity fix (long word writes
to byte wide WD33C93 registers.. not the first time Commodore ignored
their own programming guidelines.. )

This is broken.. (explains 36.xx and older superkickstart freeze)

HDToolbox problems are solved (no more incorrect size or errors from "read configuration from drive")

Next beta "soon"..

[Toni Wilen]

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

Beta 4:

- return SCSI-1 style inquiry response when using A590/A2091 SCSI emulation (Old HDToolbox compatibility fix)
- do not crash with "out of bounds" error if SCSI emulation tried to read/write non-existing HDF block(s)
- SCSI READ CAPACITY PMI-bit emulated, HDToolbox "Read configuration from drive" compatibility fix
- A3000 1.3 SuperKickstart support implemented (includes "bonus" code remapping to 0xf00000 area)
- JIT on/off switching via uae-configuration re-enables direct mode
- added MOVEC registers and PC to r <reg> <val> debugger command
- A4091 ("A3090" says driver string in ROM...) Z3 card autoconfig and ROM loading implemented (pointless, no NCR53C710 SCSI chip emulation yet, same infinite loop as with A4000T KS3.1 built-in SCSI driver)
- A590/A2091 Guru ROM adapter emulated, driver does not yet work, uses not yet emulated WD33C93 features.
- real SCSI device support (via hardware emulation) is not really working. It isn't so easy to implement after all..
- copper writes are now detected by memwatch break points (note: writes only, freeze not possible. copper is a special case)

[Retro-Nerd]

- JIT on/off switching via uae-configuration re-enables direct mode

This is still not working properly, Toni. As slows as before, very strange.

[billy]

Originally Posted by Toni Wilen

- A3000 1.3 SuperKickstart support implemented (includes "bonus" code remapping to 0xf00000 area)

No lack of a sense of humor Some of us take every beta release as a "bonus".

Defect report: 1.4.3b4 - Steps to replicate
o Launch WinUAE b4
o A3000 Quickstart Model: A3000 | Config: 1.4 ROM, 2MB Chip + 8MB Fast
o Select Disk image - SuperKickstart [symptom occcurs w/all adf's tested]
o Press Start
o Under Kickstart 1.3, click Floppy
o When KS screeen appears, middle mouse click | left click power | Reset
o Under Kickstart 2.x, click Floppy
o When KS screeen appears, middle mouse click | left click power | Reset
** CRASH dump included winuae_1434_20070602_124740.zip

[Toni Wilen]

Originally Posted by billy

Defect report: 1.4.3b4 - Steps to replicate

Can't replicate, no crashes here. Does it also crash if you do "normal" keyboard reset (ctrl+amiga+amiga)? or only if you do hard reset? (ctrl+amiga+amiga+alt) (amiga = windows keys or home and insert)

Dump file is weird, it says crash happened in WinMain() which is impossible..

btw, Windows XP + SP1? Why?

[billy]

Originally Posted by Toni Wilen

btw, Windows XP + SP1? Why?

... because it worked up till now.

Heeding your advice I updated the PC to SP2.. then I updated the ATI drivers to the latest version, updated my .net framework to 2.0 and my C++ runtimes to the 2005 redistributable.

Yes, just tried it, she does exhibit the same symptom when using CTRL+AmiL+ALT+AmiR.

Also, I can't change the ROM without a hard reset back to 1.4b, so if I perform a hard reset using CTRL+AmiL+ALT+AmiR in ROM 1.3, then load 2.x from floppy, when I perform a soft reset using CTRL+AmiL+AmiR the symptom persists.

Tried a second completely disimilar machine [work notebook always up to date because of the security dept], same symptom.
It may be something I'm doing wrong, but the symptom follows me to a 2nd PC.

OriginalPC-winuae_1434_20070602.zip
2ndPC-winuae_1434_20070602.zip

Symptom persists in Windows Diagnostic mode where all non-essential startup items and services are disabled as well.

[alanwall]

I have been having a odd thing happen when I run Amikit.
I have been getting an internet explorer/winamp error
message on my windows screen
"an error has occured in the script on this page"
referring to a winamp update.Amikit starts and runs ?
any body else ?

[Toni Wilen]

Yes, just tried it, she does exhibit the same symptom when using CTRL+AmiL+ALT+AmiR.

Still can't duplicate and new dump file is identical. I am confused. Looks like I have to test on XP later.. Can anyone else duplicate it?

JIT on/off switching via uae-configuration re-enables direct mode

Really works in next beta. Currently it may work if you enable JIT twice with different cachesize paramter (like "uae-configuration cachesize 4096" and then "uae-configuration cachesize 8192")

I have been having a odd thing happen when I run Amikit.

I hope this only happens in betas or I'll have to move this