|
Post by kram4096 on Nov 5, 2004 2:24:48 GMT -5
the snasm68k you uploaded is giving me an error that says it cant find snasm68k.e>, which is an impossible filename, I am currently runing XP SP2.
"DOS/4GW Professional fatal error (1007): can't find file C:\STEX\APPS\ROM_PR~1\G ENESIS\BASIC\BASIEG~1\DEVSTE~1\SNASM68K.E> to load"
is what is returned and I have no idea why the **** this happened. I will try moving basiegaxorz and the other tools to c:\ (on HDD2 partition1) to see if that fixes the bus
|
|
|
Post by kram2048 on Nov 5, 2004 2:25:40 GMT -5
*bug
|
|
|
Post by Tom Maneiro on Nov 5, 2004 20:50:46 GMT -5
Try installing BasiEgaXorz package into a shorter dir (like C:\bex\).
|
|
oompa loompa
I AM THE GOVERNATOR
"Git 'Er Dun!"
Posts: 1,301
|
Post by oompa loompa on Nov 5, 2004 22:50:33 GMT -5
the nt version of snasm68k should work fine with windows 2000, or xp. i doubt service pack 2 is what messes it up. long files names shouldn't be a problem either, unless i have a bug in my long to short file name converter. snasm is based on dos, and emulation for dos on the newer windows operating systems eg 2000 and xp is becoming very limited now. i probably have to find an alternative assembler now
|
|
|
Post by kram16384 on Nov 6, 2004 3:58:55 GMT -5
I have a better idea. an installer that installs basiegaxorz in c:\BasiEgaXorz and an installer for each componet (such as SNASM68k.exe and SGTD.) even changing the values in the ini file and associating with bex files. also the 0.19 version does not write to the header, which it should. and I got a wonderful idea, a new option for setting the rom serial number (ex: option ID NUMBER, "GM SR-4066A-22") and another option: option DATE, "2004.NOV" also the title isnt being set in the rom during compile nor is the allocation of SRAM
the other two options would make things more interesting
|
|
|
Post by kram8192 on Nov 6, 2004 4:15:57 GMT -5
update: why not show the sram variables on the memory map.
and maybe this change may make things more interesting:
dim foo(32, 4, 9) as byte with sram
note: 1) 3-dimensional arrays and 2-dimensional ones allowed
2) a new data type called byte (-127 to 128)
3) an added with to handle where to put the variable -sram (only works if sram is enabled), which gets rid of the need to add ext_ to the beginning of a variable name
also it would be good if all these data types were used:
*byte *unsigned byte *integer *unsigned integer *long *unsigned long *float *unsigned float *string
note that string doesnt dimension correctly to the dim command, string is an unknown type.
maybe instead of using the multiply operator, why not try this: dim a$(5, 5) as string => 3
thus creating a new operator for setting the string length
and you can then apply it to more than just dim
example: a$(8, 0) => 128 a$(8, 0) = "textTEXT" print a$ a$(8, 0) => 4 print a$
that would result in:
textTEXT text
because the string length was changed, also this lets you resize the string length of a single element.
|
|
|
Post by kram2048 on Nov 6, 2004 4:19:19 GMT -5
another idea: the <= operator
a$="foo" print <= a$
would return 128 if the string length is at its default
|
|
|
Post by kram8192 on Nov 6, 2004 4:26:07 GMT -5
correction: >> instead of => and << instead of <=
|
|
|
Post by Tom Maneiro on Nov 6, 2004 18:41:40 GMT -5
I have a better idea. an installer that installs basiegaxorz in c:\BasiEgaXorz and an installer for each componet (such as SNASM68k.exe and SGTD.) even changing the values in the ini file and associating with bex files. also the 0.19 version does not write to the header, which it should. and I got a wonderful idea, a new option for setting the rom serial number (ex: option ID NUMBER, "GM SR-4066A-22") and another option: option DATE, "2004.NOV" also the title isnt being set in the rom during compile nor is the allocation of SRAM the other two options would make things more interesting I coded an installer for v0.12... maybe it's time to update.
|
|
kramlat
Moldy Popcorn
got slack?
Posts: 42
|
Post by kramlat on Nov 7, 2004 3:46:11 GMT -5
good idea. always update the installer (.msi or .exe prefered) whenever there is an update in the program.
|
|
|
Post by Tom Maneiro on Nov 12, 2004 19:59:09 GMT -5
.MSI is too much for a litte proggy (and too complex). I prefer to use Inno Setup.
|
|
oompa loompa
I AM THE GOVERNATOR
"Git 'Er Dun!"
Posts: 1,301
|
Post by oompa loompa on Nov 14, 2004 21:54:17 GMT -5
ya tom, you should make the installers. i was doubtfully planning on it, but having an installer increases the download size to more than a meg if it's going to include the compiler, snasm, and support controls
|
|
|
Post by Tom Maneiro on Nov 19, 2004 15:44:05 GMT -5
Not if you uses LZMA (7-Zip) compression.
I'm bored, so i will update the installer later today.
|
|
oompa loompa
I AM THE GOVERNATOR
"Git 'Er Dun!"
Posts: 1,301
|
Post by oompa loompa on Nov 19, 2004 16:15:41 GMT -5
i tried that 7-zip once on snasm, and it only compressed 50k more data than just zip
|
|