Quote from: MIRKOSOFT on March 07, 2011, 09:04 PM
...

I'm searching for CD-ROM COMMANDER 128... it can be Dxx image or real diskette... no problem.


I have CD-ROM COMMANDER 64, but I'm really 128'er and I'm working except gaming in C128 mode...

...
Miro

I have the demo of v1.03 if that helps you out.  I've attached it here for you (and anyone else).  It's a zip'd .d64 image.

Referring to the RAM Expansion internally. 

Just curious as to how many ppl have given the internal expansion a go?  It remember wanting to do this years ago--never did tho.

Really no progress.  The weather this winter has been extreme as in the amount of snow and the cold.  The weather is finally breaking, tho.  I'll get this sorted out and up the .d81 images.  I'll put them all into the bbs downloads sections.  the updated BBS back ups should be on there, too (if the disks survived).

Cheers.

I talked with Brett a few years ago (probably 5+ years of so).  Didn't recall anything about being angry for whatever reason....  But the subject was never really on the agenda, either...  Anyways, i have the full versions of both Fontigus and Spraypaint.  I've taken about 3 months off from the CBM world and won't be back into it for another 2 -- busy with other living kinda things.  if you can wait.  I'll look for the rest of the Omni BBS stuff, too while I'm in my boxes.  Is that OK?

C

Quote from: megabit on November 12, 2010, 11:26 PM
...
I have the ‘How to do it yourself manual’ about ¾ finished and will
make it available when finished for anyone that wants one.

Dan…

Hi Dan,

I would be one of those ppl   The adapter I purchased from you is a real bonus.  The manual would make it complete.

cheers,
c

That's great.  I used vice 2.2 x64 and I could only get the register 6 to work properly.  Glad it works for you.

Cheers,
Carl

I tried it out and it works fine from here.  Here is the original document that I wrote 15 or so years ago about.  All I did was remove a lot of code.  Perhaps you're not in Bank 15?  if you disassemble $cdda, for example, you need to enter d $fcdda from the monitor in order to see the routine.  Here's the original mnemonics (using Buddy/Power assembler):

        10 SYS 4000
        20 .ORG $1300
        25 .MEM
        30 COLUMNS =$50         ;Set up equates
        40 ROWS =$19
        50 LDX #$01              ;Load X-Pointer with $01
        60 JSR READ             ;Jump to subroutine to read register 1
        70 EOR COLUMNS     ;EOR contents of accumulator with equate
        80 JSR WRITE            ;Write new value of Accumulator back to register 1
        90 LDX #$06              ;Load X-Pointer with #$06
        100 JSR READ           ;Jump to subroutine to read register 6
        110 EOR ROWS            ;EOR contents of Accumulator with the current number of rows       
120 JSR WRITE         ;Write new value of Accumulator back to register 6
        130 RTS                    ;Exit
        140 READ STX $D600  ;Store value of X-Pointer
        150 BIT $D600
        160 BPL READ            ;Go back and wait if not ready
        170 LDA $D601           ;Load value of current register into Accumulator
        180 RTS                     ;Return to call
        190 WRITE STX $D600 ;Store value of X-Pointer
        200 BIT $D600
        210 BPL WRITE
        220 STA $D601           ;Write value of Accumulator into the current register
        230 RTS                    ;Return back to call

If we call this program from BASIC, we would enter the following (Clear the screen and make sure that the
cursor is in the home position!):
           BANK 15:SYS DEC("1300")           <RETURN>

The entire document can be had from Tristan's website:

http://files.nothingisreal.com/publications/Monitor/Monitor_1995-02.pdf

Have a go at that and let me know what's what.

Cheers,

Carl

blankToggle =*

    ldx #$01
    jsr $cdda
    eor #$50
    jsr $cdcc
    rts

Call this routine and it will effectively blank the display.  Call it again to unblank.  It's not 'blanking' the display, but rather toggling the visible column from $50 to 0 and 0 to $50 depending on the state when its called.
You could use lda #$06 and eor #$19 for rows if you like.  Rows can change, where columns is usually always $50--making it dependable. This is nice, short, sweet, and one routine does it all.

Carl

It might be a week or more before I get back.  Just take what I've said and do a little reading on the VDC in the C128 PRG.  You'll find out that you'll learn even more things--better assembler code even--then what you thought.  All the driver does before it get's the go-ahead to do it things is monitor the stack for the address and if it's the correct address, then it will execute.  Please, just do a little reading in the RPG (like I had).  You have the answer (vdc wait/idle loop address), just head to some literature and investigate.

Let me know how you make out.

Cheers,

C

mapping the c128 is also invaluable and has a specific chapter devoted to the subject that we're talking about here.

Hey there.  I'm working on a mouse driver for the VDC--which came to be because of another project that I'm programming; it'll never get finished if I keep this up...  anyways...  I came up with the same sort of thing that you are describing: misc characters dumped on the VDC while printing during interrupts.  I don't have my source around (I'm half way across the country at the moment) but maybe this can point you in the correct direction. I waited for the VDC to be finished with it's chores first and then I allowed my driver to execute and print to the screen.  In a more specific way of saying, I waited for the stack to have an address that pointed to the vdc wait loop.  When that address was true, I then allowed the driver to print to the VDC.  I'm sure that there's more ways to do this, but this was a quick and effective way of displaying to the VDC during an IRQ without screwup the VDC's own housekeeping.  Sorry, but I cannot remember the exact address for the VDC wait loop at the moment.

If I had more time I'd put some effort into making this a little more easier to read and follow.  I hope this gets you on the right track.

C

The C128D JD comes with a ROM for the C128/64 kernal (in one ROM) and one 1571d ROM.  JD works in 128 mode & 64 mode without needing anything else.

Cheers,

C

Oops.  I gave the incorrect link (well, for Pandora and Commodore 128 emulation)

http://pandora.dcemu.co.uk/

C

Hey I like that mobile one!  I'm doing mine on the Pandora, though.  It was well worth the wait.  Been playing with this dev unit and it kicks some serious hearts.  I hope ppl start to use it.

http://www.open-pandora.org/

Cheers,

C

If there is any interest, I have built PPC64 rpm of vice 2.2 free of dependencies.  It intended for my PS3, but should work fine for any other 64bit PPC LINUX using rpm distro's.  if you want it, let me know and I'll pass it your way.  Bard's Tale and The Pawn in hi-def is really quite a treat with wireless keyboards and joysticks.  I haven't put away the game in over four hours.  lol.

Cheers,

C

If the CN12 is properly connected, then I really have no other help for you other than the drive worm might be stuck.  A quick little push with your finger will usually unjar that.  The data cables on the side of the drive would usually give you some sort of error.  Could also be the logic, as well.  IC102 (I think) is the chip that is the drive's kernel.  I wish I could help more, but I don't know too much about the '71d other than that.

C

Have you checked the CN12 interface on the board just behind the drive?  It's the one with the black cable attached to it.  it it's not properly installed (or not installed), this problem you're having will happen.

C

Just a slight problem...  I turned on my C128D last night for the first time and noticed that the 40 column display was shot as well as the keyboard...  I can deal with the keyboard, but the VIC II seems to have no colour and the B&W shades look like cycled colours....  This happens in both C128 40 and C64 mode.  Would anyone out there have any experience with this situation.  Would anyone out there have a trash C128 that I could rape the 8701 clock gen from?--I'm assuming that this is the problem unless there's a better idea out there.

My 128Megabit works great in VDC mode though!  Groovy   Thanks Dan!

Thanks in advance for your thoughts about this.

Cheers,

C

I'm assuming this: you have formatted the partition as a dos partition when you created the partition.  Sorry, for the overuse of the word partition in that last sentence...  partition.  partition.  he he.  Another 'quirk' of the '81 is that when it encounters an i0: command, it will jump out of any partition and send you back to the root directory.  I'm not too sure if a clrchn kernel call or something else in your other code is cosing an init to the '81 or not.  Just a thought here, but if you redirect the i0: command at location $198 in the '81s RAM to an RTS instruction, your problems might stop.  I don't know off-hand if an clrchn will initiate an init or not.  That is all my head has in it on this topic at the moment.

C

Is this what you're looking for?:

print#15,"m-r";chr$(0)chr$(28)chr$(1):get#15,a$:a = asc(a$)and16

if a = 16 there is a disk in the drive.  if a is clear, then there is no disk in the drive

I did this years ago with a 1541.   I used to check for a disk in the drive and then wait until one was present.  One thing about this is that you cannot tell if the drive door is shut or not...  still not 100% fool proof.

The version is at the most recent as of the time that they were sent.  If, somewhere in thos sysop text files, you can find a thread with versions or whatever, then that would be a sign as to the latest version on the disk in the archive.  in other words, the updates mentioned in the sysop texts are included on the diskettes and there were other updates after the fact.

I'll try and finish this up at the end of this week.  I still have a tonne of snow to dig threw in order to get to the garage door.  And I have my midterm's to deal with too, during this week off of classes.  A lot on my plate.

C

Just a quick piece of info for those wishing to get this running, each header should have it's own partition.   Partitions are setup from the setup option at the beginning of the boot process.  Everything else is done from within the SYSOP menu.  I used Spraypaint for the cg movies and menus and all that.  AcidDraw I used for the ansi menus (this is free now).  The BBS is uncompiled BASIC and relies on ML were speed is really needed.  I'd renumber the programs in an emulator using warp before sending it to a real 128.

When I have a little free time, I'll try out the tcpip serial kernal patch or process or what ever that was from Brain.

If you need more info please ask.  I'm working on the games disk and the other doors.  I'll get out when I can.  Midterms are coming up after suicide week so my time is limited at the moment.  If someone else has these files, I'm sure I'd be interested in them, too--in case I did miss something.

Cheers,

C

Hi,

I've been looking all over the place for info about this and I keep getting the same exact spec's -- cut and paste....   While the unit says it 64 and 128 compatible, I have no idea what that means; 128 mode compatible?  Is there any users out there that might know this?  Is it compatible with the 128 as in c64 mode?

Thanks,

C

Omni will not run under VICE (at least not with my settings) as I had stated in my earlier post.  I use winvice_64; fails.  VICE compiled for LINUX 64bit also will not load properly.  precompiled Winvice has not swiftlink/turbo option, where my compiled version of LINUX vice does.  nothing works that I've tried...  but then again, I haven't really spent more than an hour on getting it going.

C

Ahhhh...  Nothing like replying to myself   ha ha.

Anyways, I've included a simple readme.txt in the .zip.  I could not get a good copy of the games / doors disk (yet).

What's included in the .zip is Omni 128 BBS.d81 (original that was sent to me--untouched), Omni extra programs.d81 (some extra Apps including P.term and p.RLBackup, etc + all the system menus.  Again untouched.  The menus that Bell sent out were the ones from CMD's BBS), Omni sysop text.d81 (Info needed to manage the BBS and the network + how to program modules yada yada yada).  3 .d81 images in total.

A few points about the BBS, it has a macro function and a few other goodies like stackable commands and all that.  usually there are 4 menus per function/screen 40 cg, 80 cg, ansi, and ascii.  It will default to your logon mode and then work it's way down.  if you logged onto the system under 40 column cg, then it will look for the 40 column menu and then the ASCII.  I can go on about all the interesting hidden features and such, but this would get long...  too long..  this is a huge BBS.  It's also uncompiled BASIC working with ML when speed is needed.  Ideally, this was to be run from a RAMLink or CMD HD.  But now a days, it would work well with a uIEC just the same.

Any questions, please ask.  I'm sure I could remember something to answer the questions.  Have fun with this; nothing but good memories

C