|
Post by VDC 8x2 on May 29, 2016 4:51:16 GMT
This is the area to discuss programming drives of types, from tape drives to hard disk, and everything in between.
|
|
|
Post by VDC 8x2 on May 25, 2016 15:30:23 GMT
It could be basic rounding numbers off behind the scenes.
|
|
|
Post by VDC 8x2 on May 17, 2016 13:57:05 GMT
Maybe, multicolor mode?
|
|
|
Post by VDC 8x2 on May 15, 2016 19:36:42 GMT
How would you do a pointer in a banked system like the 128?
.a could be the bank. 128 and higher would refer to external mem. less than 128 could refer to internal ram. .x would be low byte .y would be high byte
I don't think that would work. I am just throwing ideas at the wall to see what sticks.
|
|
|
Post by VDC 8x2 on May 15, 2016 0:39:36 GMT
subtract 2 from address, if I remember correctly.
|
|
|
Post by VDC 8x2 on May 15, 2016 0:33:10 GMT
25 $19 Horizontal smooth scrolling and control Bits 0-3: These bits can be used to smoothly scroll the screen horizontally. The use of these bits depends on the version of the VDC in your 128. (The version number can be determined by reading bits 0-2 of the external communications register at 54784/$D600.) For version 1 of the VDC, which includes most 128s, this register should be initialized to the maximum character width (in bits 4-7 of register 22/$16). Each decrement of this register shifts the display one pixel to the left. For the older version 0 of the VDC, these bits should be initialized to %0000. In this case, each increment of these bits shifts the display one pixel to the right.
You probably need to account for bits 0-3
|
|
|
Post by VDC 8x2 on May 14, 2016 20:04:13 GMT
The MLM starts after a brk command. The brk command puts the program counter and the status reg on the stack.
The MLM get the value from the stack and adjusts.
|
|
|
PicoOs
May 12, 2016 6:11:58 GMT
Post by VDC 8x2 on May 12, 2016 6:11:58 GMT
Overview
pico]OS is a highly configurable and very fast real time operating system. It targets a wide range of architectures, from the small 8 bit processors with very low memory till huge architectures like 32 bit processors with lots of memory.
Features
pico]OS is currently divided into two layer. The pico-layer (the core of the operating system) includes this features:
Scheduler:
two modes: standard priority based or round robin preemptive multitasking max. 64 tasks on 8 bit processors, max. 1024 tasks on 32 bit processors round robin: max. 8 priority level on 8 bit processors, max. 32 priority level on 32 bit processors
Events:
the number of events is unlimited semaphores mutexes flag events
Message Boxes:
one built in message box per task unlimited box size, messages are collected messages can be pointers or huge buffers
Timer:
autonomous running timer, the system timer interrupt is used as timebase timer can work in one shot mode or in auto reload mode when a timer expires, it triggers a semaphore event
Software Interrupts:
up to 256 simulated software interrupts on 8 bit processors can be used to interface fast hardware interrupts outside the scope of pico]OS to the operating system
Miscellaneous:
atomic variables blocking and nonblocking lists debugging support allows access to internal structures
The optional nano-layer supports:
Bottom Halfs for interrupt service routines Multitasking able console I/O Multitasking able dynamic memory management Standardized API for easier task creation Named tasks, semaphores, mutexes and timer CPU usage measurement
|
|
|
PicoOs
May 12, 2016 6:08:09 GMT
Post by VDC 8x2 on May 12, 2016 6:08:09 GMT
picoos-1.0.4.zip (904.39 KB) Has anyone messed around with PicoOs? I downloaded the source and looking at the code.
|
|
|
Post by VDC 8x2 on May 1, 2016 15:49:26 GMT
If you were doing replacement roms for 128, what would you fix and or replace?
I would fix the bank jmp/jsr routines.
|
|