Do not know if this is done on purpose but... - After a "Release Mouse" it used to be that you just had to click anywhere in the Steem emul windows to "take over mouse". In 3.5.0 you need to click the arrow run in upper left. This is OK but annoying.

- I have placed the Steem 3.5.0 executable in a directory where Steem 3.2 was run. I started 3.5.0 exec, did a reset, and clicked run but Steem never started. I had to remove several state and the .ini file to make it work?

EDIT====- Interesting I thought the version of 3.5.0 that I have build was not working. But in fact the problem was with this state files! Now version done with VS2012 is working fine

- FYI: I still have a problem with the debug build. The program crash and when i start the VC++ debugger it breaks on an assert line 246 of fdc.cpp : ASSERT(shifter_freq==50) if I continue it works fine untill next time it reaches the same assert (related to motor spin up time)?

DrCoolZic wrote:Do not know if this is done on purpose but... - After a "Release Mouse" it used to be that you just had to click anywhere in the Steem emul windows to "take over mouse". In 3.5.0 you need to click the arrow run in upper left. This is OK but annoying.

- I have placed the Steem 3.5.0 executable in a directory where Steem 3.2 was run. I started 3.5.0 exec, did a reset, and clicked run but Steem never started. I had to remove several state and the .ini file to make it work?

EDIT====- Interesting I thought the version of 3.5.0 that I have build was not working. But in fact the problem was with this state files! Now version done with VS2012 is working fine

- FYI: I still have a problem with the debug build. The program crash and when i start the VC++ debugger it breaks on an assert line 246 of fdc.cpp : ASSERT(shifter_freq==50) if I continue it works fine untill next time it reaches the same assert (related to motor spin up time)?

- For mouse, check SSE option page 'Capture mouse' and General page 'Start emulation on mouse click', it could be unchecked.- When you have strange crashes, it may be a good idea to delete auto.sts, sometimes it really messes up. Ini should be safer.- The ASSERT you mention, it was because 'accurate' mode was assumed to operate at low res for games/demos in 3.5.0.I made something better in 3.5.1.

Question:If I do not have any disk in drive A then the system boot from drive C (the option When drive A is empty boot from C is set in Hard Drives form). In this case the programs located in AUTO folder are executed as expected. Now if I mount a "blank" (just formatted) FD (using .st image) in the Disk Manager form and reboot the system, the system still boot from C drive? Is this normal? Even more strange in this case even though it uses the DESKTOP.INF file and mount the C drive it does not excute any programs located in the AUTO folder ???

DrCoolZic wrote:Question:If I do not have any disk in drive A then the system boot from drive C (the option When drive A is empty boot from C is set in Hard Drives form). In this case the programs located in AUTO folder are executed as expected. Now if I mount a "blank" (just formatted) FD (using .st image) in the Disk Manager form and reboot the system, the system still boot from C drive? Is this normal? Even more strange in this case even though it uses the DESKTOP.INF file and mount the C drive it does not excute any programs located in the AUTO folder ???

Thx for the report.I've already seen strange behaviour with HD/boot.One day I'll look into it.

Considering that strange boot behaviour: it is actually TOS imperfection, to say so. During warm boot, system variable bootdevice remains as C, after C boot session, and will boot from hard disk, again. Correction in Steem would be to delete (set to A) that system variable when there is regular floppy in drive A. Or disable C in some way ...

Famous Schrodinger's cat hypothetical experiment says that cat is dead or alive until we open box and see condition of poor animal, which deserved better logic. Cat is always in some certain state - regardless from is observer able or not to see what the state is.

Famous Schrodinger's cat hypothetical experiment says that cat is dead or alive until we open box and see condition of poor animal, which deserved better logic. Cat is always in some certain state - regardless from is observer able or not to see what the state is.

Bit of a strange regression, but... if you turn on the 'record' option in the sound control panel to record ST output to a WAV file you can no longer hear any sound coming out of the speakers in (at least) 3.5.3 and 3.5.4. The sound does record okay to the file but if you can't hear what's being recorded it's a bit difficult to know when to stop.

This did work okay in 3.5.0 (I've still got a copy of that kicking around for when I want to record).

Thanks for all the hard work updating Steem, it's great to see it up and running again!

Bit of a strange regression, but... if you turn on the 'record' option in the sound control panel to record ST output to a WAV file you can no longer hear any sound coming out of the speakers in (at least) 3.5.3 and 3.5.4. The sound does record okay to the file but if you can't hear what's being recorded it's a bit difficult to know when to stop.

This did work okay in 3.5.0 (I've still got a copy of that kicking around for when I want to record).

Thanks for all the hard work updating Steem, it's great to see it up and running again!