Activity for Steem SSE
-
Steem SSE released /Steem SSE Beta/Steem_SSE_Beta_420_R24.7z
-
-
STeven committed [r1413] on Code
long path fix + fix Unix build
-
Nuke config wrench icon
-
Long path support rationalization
-
-
-
Long path support (sure it's working ;)
-
Split WriteDir into UsersPath and TempPath
-
It's more involved. Keeping everything in one folder is also Steem's way since the beginning. I'll think on it.
-
necros posted a comment on discussion Steem SSE Bug Reports
why not redirect it to system TMP folder?
-
I could make temp files visible instead of hidden, perhaps optionally.
-
@steven-seagal cra5e61.tmp , craff* if it`s tmp files why not use system tmp variable path? hidden . *.tmp files should scare users)
-
-
cra5e61.tmp craff* if it`s tmp files why not use system tmp variable path? hidden . *.tmp files should scare users)
-
cra5e61.tmp craff* if it`s tmp files why not use system tmp variable path? hidden . *.tmp files should scare users)
-
Hi What are those names (including extension) please?
-
subj
-
-
VS2008 compatibilty
-
Yes, I think TOS wants the old 8.3 DOS format. I'll add a note about this in the manual.
-
Paul Young modified a comment on discussion Steem SSE Bug Reports
Thank you, I resolved the problem by changing the name of the folder on my PC hard disk where the files were not not visible to STEEM SSE when opening the emualted GEM file open window. I think the problem might have been that the original folder name contained too many characters? Would that make sense?
-
Thank you, I resolved the problem by changing the name of the folder on my PC hard disk where the files were not not visible on STEEM SSE. I think the problem might have been that the original folder name contained too many characters? Would that make sense?
-
Thank you, I resolved the problem by changing the name of the folder on my PC hard disk where the files where not visible. I think the problem might have been that the folder original folder name contained too many characters? Would that make sense?
-
Cyprian posted a comment on discussion Steem SSE Bug Reports
R22 works fine. many thanks for the support STeven
-
Hi thx for the report and the test program. I hope it's fixed in beta R22.
-
Hi, Stated like this, the problem isn't clear. If it's not confidential or copyrighted, could you upload an archive of the folder and tell which files don't show so that it can be tested?
-
-
-
fix raster rendering display max
-
I have set up a folder for an emulated hard disk called "EColon" on my Windows 11 hard disk and installed it succesfully on my Steem SSE GEM Desktop. From the GEM Desktop, I can sucessfully select the files I have copied into "EColon" and it's folders and use the files contained within them. However, when I select a couple of the folders in the same "EColon" folder the GEM desktop window reports 0 bytes and the files in that "EColon"folder are not visible like they are in the other "EColon" folders....
-
test app and screenshots attached
-
Hi, when I switch border from Off/Normal/Large to Max then my synced with the beam code is delayed a bit (one bus cycle?) I'll prepare a small example later. Regards Cyprian
-
create branch for v4.2.0 releases
-
-
-
Debugger: bitmap browser +
-
l12n posted a comment on discussion Atari Steem and the Rest
Hi, OK, thanks. More generally I'm interested in any tip (or enhancement ;-) to help understand games (understand what they're going when "race the beam", how they draw a screen, etc). The best debugger I've found in that regard is C64 Debugger (even though I acknowledge it could not be adapted as is to the ST world), but the Steem SSE debugger is pretty powerful!
-
Hi, For the blitter, you should use a stop on "Write to $FF8A3C" in a memory browser, the interrupt isn't used. There's no feature to display a memory area as graphics, I'll think on it.
-
R16 (Windows + Linux) Fix Getbpb() and Fsnext() in GEMDOS emulation (Geneva/NeoDesk) 02 June 2024
-
-
-
-
-
-
-
-
-
tag release v4.1.2 R16
-
fixes for v412R16
-
I'm trying to use Steem SSE debugger to try to understand how famous ST games implemented their animation, but haven't had much luck so far. For example, in Pacmania (STE version) I am trying to capture when graphical resources are blitted on the next frame. I tried setting a breakpoint on blitter calls but they never break. Also, there doesn't seem to be a way to "lock" the video output to another area of memory, like the next frame. Or is there a way and I haven't looked at the right place? Any...
-
Old Guy Geek posted a comment on discussion Steem SSE Bug Reports
Just saw your response. Took only a minute or two to copy over my .ini files and BAM all the accessories worked AND no A: drive prompt! You are the man!!!!!!
-
Hi, Thx for the report. It's not you, it's Steem. You failed to provide useful links but I found the software. Seems to be 2 different bugs indeed. It's surprising this problem didn't come up before (who uses Steem SSE, right?) Please try the new beta R20, those problems are fixed (but maybe there are others now). https://sourceforge.net/projects/steemsse/files/Steem%20SSE%20Beta/Steem_SSE_Beta_420_R20.7z/download
-
-
-
fix old bug F_SNEXT (Geneva/NeoDesk) +
-
I just noticed that the attachments didn't get posted.
-
Hi, I've been preparing a tutorial to show how to install/use NeoDesk4 with Geneva. As with all my YouTube tutorials, I use Steem to demonstrate. Steem has been invaluable in running various ST software. But this time, after weeks of testing I'm stumped. Rather than a boot manager, I run Steem using a separate folder for each type of use. For example, I have a C: drive folder called CNeoDesk4. In that folder I put all the usual directories and files needed to boot from that drive. Similarly for other...
-
-
-
Option Instant machine change
-
Debugger: can find symbol
-
It's a feature, not a bug
-
Great! Then it's not a bug!
-
Hi Steven, Today I checked R18 64bit three times and this error occurred only once.
-
Hi Cyprian, Failing to relocate is a big bug but I start some random programs and they work. I suppose it happens with GEMDOS HD emu. Would you have an example program which triggers the bug? Failing that, do you you know which beta revision started the trouble (before R18)? Is the bug present in the 32bit build as well?
-
Hi Steven, I observed that when the CPU is in e.g. 32MHz mode and I use "Run to scanline n" then the image is shifted up. When I press Run button , then it looks ok. Thanks Regards Cyprian
-
Hi Steven, attached you can find Debugger v4.2.0 R11 vs R18. As you can see, in case of R18, addresses in $F1F8/F1FE/F204 are not relocated. Thanks Regards Cyprian
-
Hi Steven, I observed that when I run Steem (32bit and 64bit) from time to time no RAM memory radio button is selected. Regards Cyprian
-
Hi Steven, I observed that when I run Steem from time to time no RAM memory radio button is selected. Regards Cyprian
-
R15 (Windows-only, debugger only) Debugger bugfixes (see Steem SSE Debugger 4.1.2.rtf) 07 April 2024
-
-
-
-
-
Debugger: v412R15 fixes
-
tag release v4.1.2 R15 (debugger-only)
-
Debugger: fix crash when ST sending string to TRACE
-
Thx for your reports. I'll release fixed beta and v4.1.2 versions of the debug builds this weekend.
-
Thx for your reports. I'll release fixed beta and v4.1.2 versions of the beta builds this weekend.
-
Blanchard Samuel posted a comment on discussion Atari Steem and the Rest
Hi Steven! Sorry for the delay. It works perfectly with this version!
-
Please try with these.
-
Odd, 3 bombs is address error. I'll check with your test code later.
-
Always 3 bombs
-
Oops... Is it better with these builds?
-
Unfortunately the log function doesn't seem to work (3 bombs). I'm in supervisor mode and here is the code: ; STEEM test move.l #$456D753F,D6 move.l #$456D753F,D7 move.w #37,-(sp); Offset 0 trap #14; Call XBIOS addq.l #2,sp ; Correct stack ; Steem version in D0 => OK move.l (a0),d0 ; Write string in logs => 3 Bombs move.l #TEST_STEEM,$f0(a0) SECTION DATA TEST_STEEM: dc.b “HELLO!”,0
-
Unfortunately the log function doesn't seem to work (3 bombs). I'm in supervisor mode and here is the code: ; STEEM test move.l #$456D753F,D6 move.l #$456D753F,D7 move.w #37,-(sp); Offset 0 trap #14; Call XBIOS addq.l #2,sp ; Correct stack ; OK, I've got the Steem version in D0 move.l (a0),d0 ; Write string in logs : here 3 Bombs move.l #TEST_STEEM,$f0(a0) SECTION DATA TEST_STEEM: dc.b “HELLO!”,0
-
Unfortunately the log function doesn't seem to work (3 bombs). I'm in supervisor mode and here is the code: ; STEEM test move.l #$456D753F,D6 move.l #$456D753F,D7 move.w #37,-(sp); Offset 0 trap #14; Call XBIOS addq.l #2,sp ; Correct stack ; OK, I've got the Steem version in D0 move.l (a0),d0 ; Write string in logs : here 3 Bombs move.l #TEST_STEEM,$f0(a0) DATA SECTION TEST_STEEM: dc.b “HELLO!”,0
-
Unfortunately it doesn't seem to work (3 bombs). I'm in supervisor mode and here is the code: ; STEEM test move.l #$456D753F,D6 move.l #$456D753F,D7 move.w #37,-(sp); Offset 0 trap #14; Call XBIOS addq.l #2,sp ; Correct stack ; here 3 Bombs move.l #TEST_STEEM,$f0(a0) DATA SECTION TEST_STEEM: dc.b “HELLO!”,0
-
Unfortunately it doesn't seem to work (3 bombs). I'm in supervisor mode and here is the code: ; STEEM test move.l #$456D753F,D6 move.l #$456D753F,D7 move.w #37,-(sp); Offset 0 trap #14; Call XBIOS addq.l #2,sp ; Correct stack move.l #TEST_STEEM,$f0(a0) DATA SECTION TEST_STEEM: dc.b “HELLO!”,0
-
So I checked and it seems that the feature already exists and is documented in the manual. Look for "Emu detect": $ffc1f0 write source string to log (Debugger) You write a long to that address, containing the address of the string, 500 chars max. I don't know if it works. What I could do is remove the need for Supervisor mode and Emu detect procedure, only the 'Emu detect' setting would be necessary, as for breakpoints.
-
Debugger: support for TOS symbols floppy + ACSI +
-
Yes, and the debugger should also soon display TOS symbols of executables. Working on it.
-
That would be awesome!
-
Hi Samuel, Good idea, I'll check if that's possible, at least for a string.
-
Incorrect, it's in the beta. Works for me at least. Maybe try with options Windowed Borderless Mode and Fullscreen GUI. Fullscreen GUI isn't really supported by Microsoft with "true" fullscreen modes.
-
Hi Steven. Today I use move.b #0,$FFC123 to generate a break and debug on Steem but sometimes it would be more practical to send traces and consult a log. Is there a way to send string or simple trace to Steem from an application written in assembly? Thanks a lot.
-
lp69 posted a comment on discussion Atari Steem and the Rest
hi Steven, this is not in the beta, correct ? Also I'd love a real pause command, as F12 exits full screen again :)
-
-
1 >