|
Post by buzbard on Sept 28, 2015 15:12:09 GMT
|
|
|
Post by buzbard on Apr 21, 2015 11:46:41 GMT
|
|
|
Post by buzbard on Apr 21, 2015 11:38:51 GMT
However I did find that in FireFox there is a free add-on (well, suggested contribution $1) for off-line browsing. Still testing, but so far it works. Firefox already has "Work Offline" in the File menu, is that different from the add-on that you found?
|
|
|
Post by buzbard on Apr 11, 2015 16:12:17 GMT
I remember ads for the C64, stating it was the first home computer under $600 C64 ad (1982)It was advertised for $595. When you add tax to that and it went above $600.
|
|
|
Post by buzbard on Apr 3, 2015 16:02:28 GMT
I'm not sure, I've never owned one with a square REC. I've seen other messages where people are having problems using eproms in their REUs. I don't remember which REC they had, or if it was mentioned, but I thought I'd mention it anyway, just in case.
|
|
|
Post by buzbard on Mar 29, 2015 15:06:12 GMT
I have a 1750, I installed a socket and haven't had any problems using eproms in it. Right now I just have the KEYDOS ROM installed since it's the only one I use with the REU. When I installed the socket I also put pins in the jumper points so I could use small jumpers to adjust the settings (no more (de)soldering jumpers).
BTW: My REU has the long REC not the square one.
|
|
|
Post by buzbard on Feb 25, 2015 23:11:57 GMT
Could you post the source for that? It would make debugging a lot easier.
|
|
|
Post by buzbard on Feb 9, 2015 23:48:32 GMT
The values returned by TI and TI$ are calculated values of the system jiffy clock, located at addresses 160-162($A0-$A2). The TI$ variable isn't "stored" anywhere, it's calculated each time the variable is accessed.
162/$A2 is updated every 1/60 of a second.
161/$A1 is updated every 1/60 * 256 of a second or every 4.27 seconds.
160/$A0 is updated every 4.27 * 256 seconds or every 1092 seconds or every 18.2 minutes.
The Kernal SETTIM($F665) and RDTIM($F65E) routines can be used to set/read these locations.
There is a BASIC routine at 31096($7978) that evaluates the TI & TI$ variables, among others.
|
|
|
Post by buzbard on Dec 3, 2014 11:56:54 GMT
Ok, you caught me in a technicality, what I should have said is, The 3 lines dealing with additional sectors is ignored by the new sd2iec firmware if no disk image is mounted. This was added to the firmware November of 2013 to allow auto-booting directly from the SD card without mounting a disk image. The file "bootsect.128" is a simulated boot sector and to quote Ingo Korb, "Attempts to access other sectors are rejected." This works very well for automatically mounting and booting a disk image such as CP/M or GEOS on power-up. Thanks for the "trivia", I hadn't really thought about large sector loads like that. How would you load more than 256 sectors since you only have one byte for the number of sectors?
|
|
|
Post by buzbard on Dec 2, 2014 18:19:43 GMT
Here's a DASM source to build an autoboot sector for your disks, it also works with the latest sd2iec firmware, just compile, rename the resulting .bin file to "bootsect.128" and save it to your SD card. Note: The 3 lines dealing with additional sectors is ignored by the new sd2iec firmware. bootsect.asm ; C128 boot sector. (T1, S0) ; Compile without a load address. {-f3}
processor 6502
org $b00
byte "CBM" ; Autoboot signature.
word $0000 ; Load address for additional sectors. (T1, S1) byte $00 ; Bank number for additional sectors. byte $00 ; Number of sectors to load.
byte "MENU", $00 ; Boot message: "BOOTING..."
byte "", $00 ; Program to load on boot.
start ldx #<cmd-1 ; Lo-byte of cmd - 1 ldy #>cmd ; Hi-byte of cmd jmp $afa5 ; Execute BASIC command.
cmd byte "RUN", $22 ; The RUN" command. byte "MENU" ; Program to "RUN".
org $bff, $00 ; Fill remaining bytes with $00 up to 256 bytes. byte $00
If you modify this to work with other compilers, post it here for the benefit of others.
|
|