WinUAE 1.6.0 beta series (was 1.5.4)

[Shoonay]

my partitions are back in business, thanks Toni!

[Toni Wilen]

Originally Posted by ceztko

Wouldn't be better to use an euristic that detect UTF-8/UTF-16? According to http://www.unicode.org/versions/Unicode5.0.0/ch02.pdf , pp. 36, "Use of a BOM is neither required nor recommended for UTF-8...".

I know. This wasn't meant to be complete support yet, just simple support for files written by winuae (MSVC c-runtime always writes the BOM)

[ceztko]

Originally Posted by Toni Wilen

I know. This wasn't meant to be complete support yet, just simple support for files written by winuae (MSVC c-runtime always writes the BOM)

Nice! A curiosity: if you know a way to change that behavior of MSVC (IDE and runtime), let me know.

[Toni Wilen]

Originally Posted by ceztko

Nice! A curiosity: if you know a way to change that behavior of MSVC (IDE and runtime), let me know.

I guess the only way is to write in binary mode..

[Genju]

Just found something else. The Prowiz feature seems to be broken. Shows random Chinese characters instead of the music file format.

[Toni Wilen]

Originally Posted by Genju

Just found something else. The Prowiz feature seems to be broken. Shows random Chinese characters instead of the music file format.

I guess you mean ripper isn't "really broken", only name is shown in wrong encoding?

[Genju]

Yes, sorry for not being clear about it. The ripped files seem to be fine, just the format name is shown as garbage.

[Marcuz]

i've fired up last beta in 2 sessions only, yesterday and today:

- yesterday it goes to workbench and has the input problem i reported in a previous beta

new thing while usually winuae sets quickconfigs to have the 2 catweasels joysticks in the two compatibility' ports and so require to manual set them to mouse*, the input configuration reverts by itself to the 2 catweasel joystick every half a minute!
(logs attached)

actually this time it goes this way:
mouse is stuck; left click un-stucks the pointer; works for about 3 seconds; stuck again

i remembered what you said about it being catweasel problem, so i closed winuae for the time being;

- today i try again, with no change done, Winuae crashes.

crash minidump and bootlog attached (please, how do i force the winuae log without GUI?)

as per bootlog, the problem is prolly indeed with something catweasel, but i cannot figure what; the drivers are up to date too.

last version i have tested that works is the beta 7 ( i would test some newer beta but there's a 503 service temporarily unavailable when i try to download one.)

if you need me to test something in particular, given the limited report i have, please tell. thanks!

[thomas]

Seeking in files bigger than 2GB still does not work correctly. See new test program and its output (attached).

Time on Windows directories is one hour behind

7> echo >xx
7> list xx
xx                         empty ----rwed Heute      17:32:05
1 file - 1 block used
7> date
Samstag 14-Mär-09  18:32:40
7>

[Toni Wilen]

Originally Posted by thomas

Time on Windows directories is one hour behind

I assume this isn't beta related.. (seems to be UTC time zone difference, 2 hours here)

EDIT: seek issues fixed, thanks for perfect test case

[thomas]

The choices next to uaescsi.device are corrupted.

[thomas]

I reproducebly get a Software Failure #80000008 from "UAE clipboard sharing" when booting from floppy with a HDD or HDF connected to IDE0. Also when I reset this session, I get a red flashing screen (bad ROM checksum).

It does not happen if I connect the HDD to UAE. It does not happen if I boot from HDD (on IDE0).

It happens with both A1200 and A4000 ROM / Chipset, so it is not dependant on the Amiga model.

The crash happens before the early startup menu appears.

[Toni Wilen]

Originally Posted by thomas

I reproducebly get a Software Failure #80000008 from "UAE clipboard sharing" when booting from floppy with a HDD or HDF connected to IDE0. Also when I reset this session, I get a red flashing screen (bad ROM checksum).

It does not happen if I connect the HDD to UAE. It does not happen if I boot from HDD (on IDE0).

It happens with both A1200 and A4000 ROM / Chipset, so it is not dependant on the Amiga model.

The crash happens before the early startup menu appears.

It seems to happen if disk has too old clipboard.device. Need to add device version check..

EDIT: for some weird reason it is Lock('DEVS:',-2) that crashes when booting from disk.. (clipboard sharing waits until DEVS: is available before it tries to open clipboard.device). This is confusing.. (dos bug if Lock() is called too early?)

[Toni Wilen]

winuae.net again borken, zip upload limit exceeded so 7z this time..

Beta 17: (even more fixes. do not use b15 or b16)

- module ripper text conversion fixed
- winuae.ini UTF-8 support (only new ones are created in UTF-8)
- ACTION_READ with "illegal" length or address crashed (b15)
- catweasel log information string wrong encoding fixed
- ACTION_SEEK 2G limit and 64-bit filesystem packet fixes
- configuration file handling bugs fixed (b15)
- directory filesystem date field ignored timezone (b15)
- crash dump file naming fixed (old bug)

[Marcuz]

Winuae and input work both again, thanks Toni!

[CodyJarrett]

The result of debugger commands in beta 17 is missing. The text isn't there!

For example, if you start the debugger and use the h command the window scrolls up but there is no help text.

TheCyberDruid has confirmed that this happens for him too.

[lours]

winlaunch.alib does not work anymore with Beta 17.

thx

[Toni Wilen]

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

Beta 18:

- gui debugger unicode conversion fixes (b15)
- native dll call fixed (b15)
- already existing _UAEFSDB.___ was not updated properly on NTFS volumes, "dirty" _UAEFSDB.___ data was not flushed when emulator was exited (old bug)
- non-ascii configuration strings are duplicated in UTF-8 as <entry name>.utf8. Now even japanese file names and paths work in configuration files (backwards compatible, old versions will ignore it)
- clipboard sharing: accept only v37 or newer clipboard.device
- added DD (720k) and HD (1440k) PC floppy image type to create disk option (image will be unformatted)

[PWLM]

Hi Toni,

I have just succesfully tested new beta on an AMD Sempron laptop and P4 dual-core 3GHz with A500, A600 and CD32 configs, using adf and ISO files. You are a GOD!

[lours]

winlaunch.alib works again with Beta 18.

thx

[thomas]

Amiga clipboard does not work when used for the first time (after WinUAE start or after an Amiga reboot).

Run editor (for example CygnusEd), press Amiga-V -> nothing in clipboard. Might be ok, might also be wrong, should paste the PC clipboard ?
Enter some text, mark some text and press Amiga-C -> the marking disappears, looks like it has copied the text.
Move the cursor to another place, press Amiga-V -> I get the PC clipboard instead of the text I copied before. That's wrong.

From then on the clipboard works correctly. I.e. if I mark the same text again and copy it, it really gets copied.

[Toni Wilen]

Originally Posted by thomas

Amiga clipboard does not work when used for the first time (after WinUAE start or after an Amiga reboot).

Run editor (for example CygnusEd), press Amiga-V -> nothing in clipboard. Might be ok, might also be wrong, should paste the PC clipboard ?
Enter some text, mark some text and press Amiga-C -> the marking disappears, looks like it has copied the text.
Move the cursor to another place, press Amiga-V -> I get the PC clipboard instead of the text I copied before. That's wrong.

From then on the clipboard works correctly. I.e. if I mark the same text again and copy it, it really gets copied.

Same as http://eab.abime.net/showpost.php?p=...&postcount=231 (and related posts)?

[thomas]

Yes, maybe. Seems to work correctly in native screenmodes and after changing screenmode. But does fail when booting directly into P96 screen. Strange that clipboard is affected by screenmode.

[Toni Wilen]

Originally Posted by thomas

Yes, maybe. Seems to work correctly in native screenmodes and after changing screenmode. But does fail when booting directly into P96 screen. Strange that clipboard is affected by screenmode.

It is side-effect of only transferring clipboard when winuae loses/gains focus (which also happens when switching modes) Not sure how to fix this yet..

[clenched]

b18 - Direct entry via the 'enter address' dialog box in debugger goes to wrong address. Can work around with dg and mg commands though.

[Toni Wilen]

Originally Posted by clenched

b18 - Direct entry via the 'enter address' dialog box in debugger goes to wrong address. Can work around with dg and mg commands though.

What is "enter address" dialog? Remember that I don't use or really care about gui debugger (I only use the original console version) = much more information needed.

[clenched]

Goto GUI debugger mode to either disassembly or memory window and right click mouse. A menu appears under mouse set top address> then enter address very bottom then the box shows up. Forgot to mention but paste doesn't work in this box either.

[Genju]

Portaudio device names went bork during the switch to UTF, it seems.

[gaula88@hotmail]

I've noticed a very large speed hit comparing 1.53 with beta18:
With 1.53, I could run State of The Art fullspeed without any slowdowns (in A500 mode) and with B18 I get slowndowns in some parts of the demo.
I've never used OGL/D3D modes disabled in those betas, so that's not to blame.
To put it simply: same config & program, slower with b18. No transparent leds, fullscreen, PAL 50Hz mode synced to a real 50Hz display for ultra-smoth scroll.
Should we re-gain that speed loss in the final version?

I run WinUAE in a EEEPC computer with Intel Atom 1.6Ghz processor.

Appart from that, I subscribe that portaudio device names is giving me the same problem in beta 18.
Thanks Toni!

[Toni Wilen]

Originally Posted by gaula88@hotmail

I've noticed a very large speed hit comparing 1.53 with beta18:

What does CPU% say? If it is 99% previously and 101% now -> there is always large slowdown. (every other frame will be missed, especially if vsync is enabled)

Also always test in windowed mode before reporting

EDIT: which was last "fast" beta?

[Toni Wilen]

Beta 19:

- missing command line unicode support added
- added support for winuae.exe <paths> [<other params>] command line. <Paths> can be path to a configuration file, any supported floppy disk image file or statefile, multiple paths supported, path parsing stops when first parameter beginning with '-' or '/' is detected. Automatically disables "show gui on startup".
- improved configuration parsing, now for example something="path" and command line -something="path" works, previously " (or ') was not parsed properly
- clear dsound buffer when sound autodeactivates, it was possible to have some old sound data left in buffer if buffer size is really big
- gui debugger clipboard and enter address option fixed (b15)
- autoscaled screen was off center if display size was too small
- directory filesystem "unimplemented error 3" fix
- directory filesystem "unimplemented error 87" when setting file/dir datestamp and drive is in FAT partition (FAT date range is not as large as Amiga supported date range, AmigaDOS minimum date is 1978-01-01, FAT minimum is 1980-01-01)
- directory filesystem date underflow fixed, host-side date earlier than 1978-01-01 caused underflow, result usually was date in far future.. (bug since the beginning most likely)
- updated directory filesystem date calculations to 64-bit
- directory filesystem ERROR_COMMENT_TOO_BIG implemented
- PortAudio works again, also accept only v1899 or newer library
- clear D3D filter screen when autoscale settings change
- added F13-F16 to rawkeyboard keycode array

[glue]

I have some troubles with last beta

Run WINUAE as A500 classic, Amiga run with KS 1.3 and hand show on. F12 and inserting adf file then OPEN next OK and WINUAE exit to windows.

Inc. log files

[Toni Wilen]

Originally Posted by glue

I have some troubles with last beta

Run WINUAE as A500 classic, Amiga run with KS 1.3 and hand show on. F12 and inserting adf file then OPEN next OK and WINUAE exit to windows.

Inc. log files

Run in windowed, you should get crash dump file.

[glue]

Testing on BETA 17,18,19

Run in window mode but effect is the same. Winuae close. Nothing crashdump files nothing errors all is in the log.

Beta 16 crashed on load config

After few test, i found the BUG

this error takes a stand in case of mode PA (PA WDM-KS only) in DS mode WINUAE work good.

[Toni Wilen]

Originally Posted by glue

Testing on BETA 17,18,19

Run in window mode but effect is the same. Winuae close. Nothing crashdump files nothing errors all is in the log.

Beta 16 crashed on load config

After few test, i found the BUG

this error takes a stand in case of mode PA (PA WDM-KS only) in DS mode WINUAE work good.

Did portaudio ever work? If not -> portaudio problem, not mine

[glue]

After first run winuae, i inserting adf with some game or demo and saving config. I close winuae with previous saving configuration (PA WDM-KS) and rerun WINUAE . Everything it works correctly then F12 changed adf or other settings then OK and winuae is closed.

[Ratte]

Beta 18 says ..contact the author .. so here i am.
Massage: 1026
It happend when i copyed a file with "name.ld.strip.info" from hardfile to windows-desktop (mounted as HD0: hardfile / DH1: WinDesktop) with DirOpus 4.x.

[Toni Wilen]

Originally Posted by glue

After first run winuae, i inserting adf with some game or demo and saving config. I close winuae with previous saving configuration (PA WDM-KS) and rerun WINUAE . Everything it works correctly then F12 changed adf or other settings then OK and winuae is closed.

It still can be portaudio bug

Originally Posted by Ratte

Beta 18 says ..contact the author .. so here i am.
Massage: 1026
It happend when i copyed a file with "name.ld.strip.info" from hardfile to windows-desktop (mounted as HD0: hardfile / DH1: WinDesktop) with DirOpus 4.x.

You sure it was 1026? There is no error 1026 listed in WinError.h
Can you duplicate the problem very easily?

(I found that SHFileOperation() doing delete can cause this error but you said it happened when copying?)

[Ratte]

@Toni:
Hmm ... might be possible, because it "replaced" an existing file.
I tried to reproduce the error, but without success.

Could it be possible, that it is an sideeffect of hd-buffers inside amigaos and stupid enduser (me) on he other side?


I worked with editors on the file .. on the amiga-side AND on the pc-side .. could it be possible, that aos didnt noticed his "wrong" buffers?

(just an idea)

[Xorlac]

Toni:

1.6 b19 appears to have a loading issue for the configuration data.

Repro:

1. Save a configuration with a couple disks in the floppy slots df0/df1/df2, etc.
2. Quit winuae/relaunch/load the configuration
3. Observe previous images are no longer in the floppy slots.

Previous beta version was able to load the configuration and the disks were loaded in, so save appears to be OK.