WinUAE 1.6.0 beta series (was 1.5.4) - Page 16

thomas · 22 March 2009, 15:02

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 · 22 March 2009, 15:58

Quote:

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 · 22 March 2009, 16:46

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 · 22 March 2009, 17:19

Quote:

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 · 23 March 2009, 08:24

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 · 23 March 2009, 18:37

Quote:

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 · 23 March 2009, 19:16

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 · 27 March 2009, 10:57

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

Gaula92 · 27 March 2009, 20:14

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 · 27 March 2009, 20:26

Quote:

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 · 28 March 2009, 16:50

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 · 29 March 2009, 11:44

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 · 29 March 2009, 11:47

Quote:

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 · 29 March 2009, 12:35

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 · 29 March 2009, 15:23

Quote:

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 · 29 March 2009, 15:34

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 · 29 March 2009, 16:53

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 · 29 March 2009, 16:57

Quote:

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

Quote:

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 · 29 March 2009, 20:48

@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 · 29 March 2009, 23:17

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.

23 March 2009, 08:24	#305
clenched Registered User Join Date: Sep 2008 Location: Gainesville U.S.A. Posts: 771	Small Bug b18 - Direct entry via the 'enter address' dialog box in debugger goes to wrong address. Can work around with dg and mg commands though.

28 March 2009, 16:50	#311
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	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 Last edited by Toni Wilen; 09 August 2009 at 15:35.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE 2.5.1 beta series	Toni Wilen	support.WinUAE	69	22 December 2012 10:22
WinUAE 2.3.3 beta series	Toni Wilen	support.WinUAE	124	17 September 2011 15:48
WinUAE 2.3.2 beta series	Toni Wilen	support.WinUAE	79	31 May 2011 19:39
WinUAE 2.3.0 beta series (was 2.2.1)	Toni Wilen	support.WinUAE	229	22 September 2010 19:20

22 March 2009, 15:02	#301
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	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.

22 March 2009, 16:46	#303
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	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.

23 March 2009, 19:16	#307
clenched Registered User Join Date: Sep 2008 Location: Gainesville U.S.A. Posts: 771	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.

27 March 2009, 10:57	#308
Genju Registered User Join Date: Mar 2005 Location: Germany Age: 43 Posts: 73	Portaudio device names went bork during the switch to UTF, it seems.

27 March 2009, 20:14	#309
Gaula92 Registered User Join Date: Aug 2008 Location: Spain Posts: 527	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!

29 March 2009, 15:34	#316
glue Banned Join Date: Dec 2006 Location: https://t.me/pump_upp Posts: 76	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.

29 March 2009, 16:53	#317
Ratte Registered User Join Date: Sep 2008 Location: Germany Posts: 331	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.

29 March 2009, 20:48	#319
Ratte Registered User Join Date: Sep 2008 Location: Germany Posts: 331	@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)

29 March 2009, 23:17	#320
Xorlac Registered User Join Date: Mar 2009 Location: Seattle, WA / USA Posts: 26	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.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)