| |
CreaMD
Registered: Dec 2001
Posts: 3050 |
Release id #167921 : C64Studio 5.8
Who is using this? Can you share your experience? |
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11357 |
the forum64 elite can help |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
After some screwing around I think I got the assembler syntax correct. However I cannot get a simple program to rebuild after changing a single !byte statement.
I keep getting:
Determined main.s as active document
Build is current
Running ASM File
An exception occurred: Object reference not set to an instance of an object.
And the generated .prg is still the same from the first time the assembler appeared to actually work. I closed all cmd.exe and explorer instances even displaying a path _near_ the "Solution" dir, Windows being a little flaky with that.
Never mind the tool actually running x64.exe, even with this non-updated binary.
In short: not a good experience. |
| |
Endurion
Registered: Mar 2007
Posts: 73 |
The assembled file seems fine, but the problem appears to be running the emulator.
Did you use it without solution, just the straight file?
Did you setup the emulator? |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I use a plain .asm file (C:\Users\compyx\Desktop\main.asm):
* = $0801
!word end_bas, 2018
!byte $9e, $32, $30, $36, $34, 0
end_bas: !word 0
* = $0810
lda #$0c
sta $d020
sta $d021
rts
When I open C64Studio, open that file and select compile, a main.prg appears on my desktop. Trying build and run however outputs the same error message as stated before. I "set up" VICE by setting the path to x64sc.exe. I use a VICE version only a few commits behind current trunk.
When changing the code in main.asm and selecting compile or build or rebuild, the binary isn't updated. For an updated binary I have to close C64Studio, remove main.prg and reopen C64Studio and the file .asm file and select compile.
Pretty sure I'm doing something wrong here. |
| |
Dano
Registered: Jul 2004
Posts: 231 |
I heard recept updates of Win10 get somewhat strange when it comes to stuff on desktop (like restoring deleted files).
I would try some folder somewhere else.. |
| |
Endurion
Registered: Mar 2007
Posts: 73 |
Thanks for the info. This looks like the setup of the emulator is the cause.
Is there more info to that exception?
Just to make sure, could you please compare the settings for the emulator with this screenshot? Also ensure, that in the main toolbar an emulator is actually selected.
http://www.georg-rottensteiner.de/webmisc/vice-settings.png
The non-compiling later on is a followup error. C64Studio still thinks it's in compile mode and thus doesn't re-build. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11357 |
"VICE version only a few commits behind current trunk" - was it even ever tested with it? :)
"I heard recept updates of Win10 get somewhat strange when it comes to stuff on desktop"
i have funny behaviour on desktop also on win7, also had it on XP even. the whole permission stuff and also the file-locking in windows is so broken it hurts :( |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I've moved C64Stdio into C:\, and created a directory D:\projects\c64studio-test\, which contains a single file "main.asm" (and "main.prg" once I select 'compile'".
Emu setup is as follows: https://www.dropbox.com/s/85jk572p2o6apmj/c64studio-setup.png?d..
I would expect main.prg to be regenerated when I change main.asm, just like with Makefile's.
But perhaps I should RTFM :) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting Groepaz"VICE version only a few commits behind current trunk" - was it even ever tested with it? :)
"I heard recept updates of Win10 get somewhat strange when it comes to stuff on desktop"
i have funny behaviour on desktop also on win7, also had it on XP even. the whole permission stuff and also the file-locking in windows is so broken it hurts :(
I don't know how C64Studio runs VICE, but with GTK3VICE I would at least expect to see a cmd.exe instance popping up, disappearing quickly if some arguments passed to VICE are wrong.
The whole "files on desktop" is indeed very broken. Last night I couldn't remove a VICE bindist dir because Windows decided a font file was somehow in use and couldn't be deleted (I could rename it, but it still refused to die).
Doing the only sane Windows thing was ofcourse to reboot :) |
| |
DJ Gruby
Registered: Aug 2002
Posts: 30 |
Quoting CompyxDoing the only sane Windows thing was ofcourse to reboot :)
I'd rather say doing the only sane Windows thing is removing Windows. ;) |
... 8 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 - Next |
