(deleted post)

[deleted]

This Message was deleted. This empty message preserves the threading when a post with followup(s) is deleted. If all followups have been removed, the original poster may delete this post again to make this placeholder disappear.

[Alexander Oestert]

Thanks for the link.

It works great and it works on tablets, unlike others I tried before.

[M. Joury]

Out of interest, does BEEP work for you?

-Marwan

[MichaelG]

Looks great. Does it feel great as well?

I am just curious how fast this emulator is. Could someone run the following little program and post the result?

LBL "TEST"
CLX
SETSW
100
RUNSW
LBL 01
DSE X
GTO 01
STOPSW
RCLSW
STOP

It takes 9 sec for the real machine, 1.3 sec in the V41. Btw the 32sII runs that in about 3 sec.

Michael

[Olivier De Smet]

You can change the speed only in commercial release.
The free one is about the same speed as real hardware

Actually the rom is not patched to allow a 'nice' experience at fast speed.

You can obtain x50 speed up but the keyboard debouncing is also speed-up so
key entry became difficult.

up to x4 the keyboard is usable, but after ... but you can change speed after the program is started and reverse back to x1 when finished :)

for your program : x1 : 8.37 sec, x4: 2.48 sec x16: 0.76sec max: 0.13sec
with a motorola defy (700MHz one core processor)

P.S. sound is not implemented actually, certainly later

Olivier

Edited: 20 Jan 2012, 7:18 a.m.

[deleted]

This Message was deleted. This empty message preserves the threading when a post with followup(s) is deleted. If all followups have been removed, the original poster may delete this post again to make this placeholder disappear.

[Olivier De Smet]

Be patient, I'm planning to be Hepax compliant too ;)

(and perhaps partially utils-cl compliant too)

Olivier

Edited: 20 Jan 2012, 7:57 a.m.

[Tobie Niggli]

Thank you. I allready love it ;-)

[MichaelG]

Thx for the data. They where very interesting. It took me a long while to figure out why your Android device is soooo fast or the V41 sooo slow.

My gut feeling told me a PC should be at least as fast as the Android. The result is not the PC is slow but the V41. I played around by modifying the V41 sources. Now I get down the time needed for that little program to 0.15 sec.

These 0.15 sec doesn't seem to be the end. Right now I cannot make V41 faster because the speed also influences the keyboard handling (like in the Android). Faster means the "NULL" as the response of a long (!) keystroke comes earlier -> too early, more or less instantly. Lets see whether that can be fixed...

Michael

[Guenter Schink]

Hi Olivier,

did you see my comment that the go41CX doesn't work on my Acer Iconia 500 (Android 3.2.1)? The suggested method to get a "Memory lost" doesn't work - though it does on the Galaxy I9000. Any idea or solution?

Günter

[Olivier De Smet]

Did you upgrade to the latest version (1.0.2 for go41c and 1.0.3 for go41cx) ?

The last version should display "MEMORY LOST" at first launch.

Olivier

[Guenter Schink]

Thanks Olivier,

the update did it. I also have a report on the go34c in the other thread.

Günter

[Jeff Johnson]

Oliver,

The previous version of go41c wasn't displaying correctly on my Samsung Galaxy Tab 7 (overlapping text), but 1.0.2 works great. Nice job! Looking forward to trying it out.

[Jeff Johnson]

Make that "Olivier". Sorry.