Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store  

fibrewire

Members
 View Profile  See their activity

  • Content Count

    1,689

  • Joined

  • Last visited

Posts posted by fibrewire

  1. Posted · Edited by fibrewire

    This raises the point that it might now be easier and more expedient to keep the window borders inside the byte boundaries, instead of outside as they currently are. This way, the split rectangles would always be whole byte extents. This would certainly save a bit of time when updating chunks of the desktop or clearing out sections of the display - not to mention making the window rect calculations 8-bit.

    I wonder if the RLE window mask could be used after the block blit DRS mentioned previously for shadows, corners, or just to realign/touch-up the entire rectangle! If it's fast enough, block blit DRS + RLE masks sound like an interesting way to make animations & games in the interface.

     

    I can't wait to see a video of the GUI :D

  2. Posted

    Hey i saw something in that article that might apply to your GUI if your still snapping windows to byte boundaries.

     

    "Another DRS algorithm, which is much simpler, is to divide the playing area into blocks, and mark each block that is dirty. When it is time to update the screen, blit all dirty blocks. By carefully chosing the size of blocks, an optimal speed may be achieved."

     

    Aslo, found the Apple 3 SOS Driver Writer's Reference. I don't know if it's of any use, but it's interesting that all drivers are stored in a single file, and has it's own configuration menu.

     

    Apple III SOS Device Driver Writer's Guide.pdf - Asimov.net

     

    Also, here's the Standard Device Drivers Manual for completeness.

     

    Apple III Standard Device Drivers Manual - 1000 BiT

  10. Posted · Edited by fibrewire

    I'm clearly prematurely optimizing, but perhaps you could have common routines repeated in multiple banks to avoid the LJSR overhead. It would be great if there were an optimizing assembler that could do this sort of thing automatically. Other obvious optimizations could include inlining function calls, dead code removal, peep hole optimization, etc. I could also imagine a tool that took a trace of the program and analyzed the function call sequence to automatically partition the code into tightly coupled pieces the size of one ROM bank. Anyhow, correctness should come first and then you can worry about optimization.

    Like some kind of virtual memory manager? :) <- I'm sorry i couldn't resist. It would be awesome if there is some way to prevent future program writers to avoid this hurdle with your GUI by assigning an address range for the user's program. Also, if you choose the SDX method, could someone like drac030 add the functions of the proprietary one?

  12. Posted

    JON! The text render speed is FAST - it's so cool that your code is constantly shrinking, and getting ever faster. It's impressive to see the difference when watching videos before & after the code rewrite.

     

    Could GUI modules benefit from being stored in LZ4 on a cart and unrolled into ram when accessed?

  13. Posted

    If you don't use more than four of the 9VAC power supplies, maybe using one of these or something similar would suffice for your power issues:

     

    http://www.voodoolab.com/pedalpower_ac.htm

     

    "The Pedal Power AC provides two 9VAC and two selectable 9VAC or 12VAC outputs. Features include a toroidal transformer and completely isolated outputs to insure noise free operation. It comes complete with cables and detachable AC power cord. And like all Voodoo Lab products, the Pedal Power AC is hand made in the U.S.A. and carries a 5-year warranty*."

     

     

     

    post-27823-0-59041300-1381816092_thumb.jpg

  19. Posted

    I think I have a 'Chip' in a bag somewhere - none installed that I know of.What would the Chip do for you?Worse comes to worse, I'll just build my own 'drive' and rip the tracks. I have some disks from OSS that I can't read either, so this project has been in the queue for a while.As long as there is oxide on the disk, we should be able to read it. If somebody wrote over the data... well...Bob

    I'd say let Bob have a try - and what OSS disks are in the queue :)

  21. Posted

     

    Best Electronics has a fair bit, here is a list of what I found with a quick look.

    400/800 SALT (Stand Alone Test) 2.05 Diagnostic Cartridge                         TE15644    $25.00
600XL/800XL SALT  (SALT 2.05 Format)                                             CB101077    $25.00
600XL/800XL/400/800/1200XL/XE Super SALT Universal NTSC Diagnostic Cartridge     FD100335    $30.00
Super SALT Extended Hardware Universal Test PCB(400-XL-XE Computers)             FA100332    $50.00
130XE Plug in Diagnostic Test Board                                              CB102534    $34.95
Atari 810 Factory Diagnostic Cartridge.                                          CB101129    $20.00
Atari 810 Factory Manufacturing Test Cartridge                                   CB101130    $24.00
Atari 810 CPS Field Exerciser Diagnostic Cartridge                               FD100006    $24.00
Atari 810 Factory Disk Drive Check Out Diagnostic Cartridge                      CB103035    $24.00
Dysan 5 1/4 inch SSSD 810 Alignment Disk                                         CB101156    $40.00

    I did find the alignment disk there, but was there ever an official diagnostic board as nice at the one for the 130xe?

  23. Posted · Edited by fibrewire

    Do you know where the firmware is stored ?

    On an eprom or on the hard disk ?

    Is this updatable without an eprom burner ?

    Frank

    Firmware is on the Utilitles disk, the more recent disk set from Jan '83 has the 18.3 firmware. The file is called "CF183.DAT"

     

    Firmware is written to the drive using the Corvus Utilities program. First, boot the computer win the Atari BASIC cart in the Atari 800. At the ready prompt type RUN"D:DIAG and then select U for update firmware. I'll have a new Corvus video up shortly.

  25. Posted

    Really coolsome. As for start, I try out 1 Atari 800 for now and see if it is really works. If it is really works , then I will hooks up 2 Atari 800 as communication each other ?

     

    One Atari interface is required to talk to a Corvus drive (or multiple daisy chained drives). For multiple Atari 800 computers to talk to a single Corvus disk drive, a Corvus Multiplexer is required. Also an Atari-Corvus interface for each Atari computer to attach to the multiplexer is required. It can get a little messy...

    post-27823-0-30274900-1381307864_thumb.jpg

AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2021 AtariAge

×
×
  • Create New...