|
Post by cbmguy on Oct 24, 2015 17:57:29 GMT
Well, so far (and I'm talking about 30-45 minutes with the kit), there is no rr-net type functionality. The U-II is basically an ftp server which you pass files to. Then you can access them on the c= side through the cartridge menu. I haven't gotten into it too much, but hope to in the next week. I know there's a way (it's documented) to directly access the cartridge and the data in it without the cartridge menu being active--I just haven't gotten that far yet.
ATM, I use a powered USB hub plugged into the U-II. I have the USB to ethernet plugged into the hub (purchased from Gideon) which is then plugged into my var11n bridge via ethernet for WPA2 wireless--again, the power for the bridge is coming from the usb hub. Finally, I have a usb thumb drive plugged into the hub, which is accessible to U-II all at the same time. I have one USB slot left on my hub. I wish I could take a picture and up it here because the picture is very simple and not nearly has complicated as it all sounds written out.
I use my old TFE for telnet and BBSing--the ethernet port is connected to the var11n bridge and it's all secure and wireless.
|
|
|
Post by cbmguy on Oct 24, 2015 15:31:33 GMT
Oops, I meant PM your address and I'll send you the ROM
I'm not asking for anything, so don't worry about that. When I first started getting my C= gear back and I had no serial cables, someone from the old 128 Alive board just sent me a couple without hesitation. When the cables arrived, I was taken back to when we all used to do that in the user groups--we just shared and swapped. I have a blank 27256 that I can burn off and send you.
I'm assuming it will be the 1571 rom since you have a 128dcr? Or did you want to make your own with the romkit and send me the binary?
|
|
|
Post by cbmguy on Oct 23, 2015 20:12:32 GMT
Would you like me to burn you off one? pm me if you like.
|
|
|
Post by cbmguy on Oct 19, 2015 14:59:19 GMT
FYI: With the 1541-Ulitmate II and the new firmware, you can now ftp your files to the cartridge (if you have a proper USB to ethernet device) and load up the .prg or .d64 into the 128 manually as usual with the cart. I was using the feature this past weekend and it works great.
|
|
|
Post by cbmguy on Oct 15, 2015 17:26:18 GMT
Those Flyer's look pretty slick, but they've been out of production for quite some time. I would love to see for sale again. I'm kicking my self for not buying one when I had the chance.
My idea was a little lazy, perhaps: Write the source in an IDE on the PC, press CTRL-F5 (for example) to cross compile, when completed send the binary to the Commodore. The Commodore would monitor the network for a special packet sent with the CTRL-F5 from the PC's IDE and fill its memory with the incoming binary and then execute at the specified location.
I wish I had more time... But this maybe something that will force me to get my basement organized and everything set up properly to work on.
c
|
|
|
Post by cbmguy on Oct 11, 2015 15:41:14 GMT
Is there a C128 network option that will have a Cross Assembler send the compiled code to the C128 memory? For example, using a mod'd kernal on the C128 and an ethernet cartridge that would wait for a specific packet on the network. The cross assembler would use a function that would compile the source, send a "hey you there" packet, wait for an ack back with some "here I am" info and then push the compiled bytes to that specific C128 on the network--automatically writing to the C128's memory where specified by the cross assembler.
It's Thanksgiving weekend here in Canada (gobble gobble) and with this extra time I got to playing around with my 41U-II and the new 3.0b firmware--with it comes some pretty slick networking. With the alternative kernal options in the cartridge, making a kernal with a network option to listen for a special "hello where are you" packet from a cross assembler/IDE on the network would be a little easier.
Emulators are great, but they don't compare to the real VDC of the 128. Transferring the compiled code from one source to another is getting to be such a bummer.
c
|
|
|
Post by cbmguy on Oct 3, 2015 0:38:10 GMT
|
|
|
Post by cbmguy on Sept 22, 2015 16:49:12 GMT
Maybe biggest problem isn't it doesn't have a name... I was thinking myBitch but that might be too offensive. lol good one! lol And yes, the lowercase char strings are compiled into screen codes while the uppercase are compiled into normal chr$ values. It's not very useful. I've converted the modules to 64TASS 1.51, but the .proc/.endp directive won't provide internal labels to be printed to a text file. The source code is modular and sometimes modules seem to be skipped when compiled, as if it is over looking the .include directive. It seems that each cross assembler is broken in some way or another. I've decided to take a break and build a server that will sync the source code so I can work on it at work and from home without too much hassle.
|
|
|
Post by cbmguy on Sept 18, 2015 14:09:08 GMT
Thanks for the reply. Any two cents is better than none. I love this assembler for the scoping one can do of their source code. It excels at everything, but that fundamental and (IMHO) very basic function. Unfortunately, this is breaking it for me, big time. It's making using the custom characters next to impossible on the VDC. I've asked for a .pet directive to force all char's and strings into petscii code regardless of whether the 7 bit is set or not. I'm still hoping to be told I'm doing it wrong and there's a way to make this compile properly. Cheers!
|
|
|
Post by cbmguy on Sept 17, 2015 20:23:26 GMT
Does anyone have any experience with kickAssembler? I cannot seem to figure out character strings. It seems that any lowercase characters are automatically translated to screencodes and uppercase characters are translated to petscii. I'm programming for the VDC which can use both lower and upper case sets at the same time.
The issue is this: using the following,
jsr primm .text "F1 Help F2 View" .byte 0
results with: f1 h f2 v
and sometimes some funky screen attributes (blinking, rvs, etc) occurs, too because of the way the text strings are being compiled. Besides coding each character in a .byte list, I have no idea how to change this problem.
I was asked to use the C= & SHIFT key to change character sets. Am I missing something? Is there a way to use char strings easily?
cheers, c
|
|