Maverick v5.04 on a cmd 1541 emulation partition

[dr.v]

Anyone here ever successfully install maverick v5.04 on a 1541 emulation partition?  I know the stock copy has a mild form of protection on it, so a a simple mcopy won't work.  Maybe there is a version out there which has been retooled for a native partition?  I have seen many "cmd cracks" out there, but they are mostly games.  And most of those cracks are for PAL.

[Diddl]

Maverick needs modified drives with 8K RAM expansion (RAMboard) at $6 or $8. Maybe you have to configure this RAM in emulator (VICE is able to emulate additionally RAM simply).


Some of the Maverick tools run since I got a special RAMboard (Supercard plus). I have analyzed this and found this card has 8K RAM and additionally a special ROM between $0800 and $17ff (4KB). This ROM hold some functions for reading whole tracks and other strange stuff.

With Supercard+ runs Maverick a little faster at beginning cause no upload of code is nessecary.

[dr.v]

Yep, I have a ramboard and jiffyDOS installed on two of my 1571's.  I'm even aware of the memory address changes for the 71 installation vs. the 41 installation when using the ramboard copiers.  But I don't undersatnd how that will help me put it on a 1541 emulation partition?  Maybe I'm missing something in your post.  I have seen SCPU compatible 1581 copiers that were retooled from maverick v5.  But I have yet to come across a version where a complete installation on a CMD Ramlink or HD 1541 emulation partition is possible.  Maybe someone else has or knows of a parameter that allows for this?  (I doubt the team at KJPB made a paramter for their own software).  Have any of you guys running IDE64 been able to run maverick from a HD?

[Diddl]

My english is not so good ...

"1541 emulation partition" is not really clear for me. I thought you speak about emulation in an emulator like VICE?

[dr.v]

No worries, Diddl.  I understand you just fine.  English is my first language and I sometimes have trouble with it    what I am trying to do is almost pointless (I know that).  The disk access routines in v5.04 are incompatible with cmd devices.  I thought maybe I could get an earlier version installed (going back to renegade) but no luck.  I am a problem solver by nature.  When I can't get something to work it just makes me try harder.  Even if there aren't many good reason to have maverick on a 1541 partition!

[Diddl]

I collect drives since nearly two years and I have now many drive types: 1541,1541-II,1570,1571,8050,SFD,8250 in my 8296-D.

For 1541 and 1571 I have nearly all popular parallel speeder except prologic DOS.

I'm very interested in this kind of hardware ... 

----

CMD drives are very good but very rare also, so I don't have a CMD drive. And I know nearly nothing about CMD drive hardware internals.


Maverick is the ultimate software for Commodore drives. it is very special to 1541/1571 hardware. Why do you believe it would work in a CMD drive?

Is a CMD drive so similar to a 1541 (same ROM, same IO (VIA) on same address)?

If CMD drives allow partitions the system ROM (DOS) cannot be the same. Maverick calls code from DOS ROM, if a drive has not the correct code in this address space it will fail (it must fail).

[dr.v]

Diddl - Nice collection!  I have about four 1571 drives (3+my 128DCR) and two 1581's (and a 1541-II in my closet somewhere).  I have jiffydos in all of my dirves + a couple of ramboards.  I have never heard of prologic dos.  I'll look into it. 

You're certainly correct - maverick is very special to 1541/1571 drives.  Maverick does not work with cmd products (well, as far as copying to emulation partitions on a ramlink or hd).  I wanted to have maverick on my ramlink/cmd only to boot the software.  This is just a matter of circumventing whatever disk boot protection KJPB used.  What you said is true, Diddl.  The DOS rom is not the same and when maverick makes it's disk access routine calls, the software hangs (fails).

Many years ago (about 20) when I was a teenager I was extremely involved with the c64/128.  I ran a BBS, was active in my local users group, did a ton of 8 bit assembly coding, helped repair C= equipment, etc.  Then I graduated from high school, went off to college, and gave up my time consuming hobby.  Even sold off my equipment.  14 years of college, 4 degrees, and 1 tenure track university position later I decided that it was time for me to return to my passion for C=.  You can imagine how excited I was to find all of the people here (people like you, Diddl) who helped keep the faith over the many years.     

[Diddl]

Many years ago (about 20) when I was a teenager I was extremely involved with the c64/128.  I ran a BBS, was active in my local users group, did a ton of 8 bit assembly coding, helped repair C= equipment, etc.  Then I graduated from high school, went off to college, and gave up my time consuming hobby.  Even sold off my equipment.  14 years of college, 4 degrees, and 1 tenure track university position later I decided that it was time for me to return to my passion for C=.  You can imagine how excited I was to find all of the people here (people like you, Diddl) who helped keep the faith over the many years.   

Yes! Same here.

As a teenager I did many programming on 4032 and 8032 computers. Later I got a C-64 and was happy with it. Many years I forgot commodore while working on PC's and mainframes.


In 2008 I found my old floppy disks and wanted to get their contents on my PC. I was very amazed cause this big community! For 4040 and 1541 it would be simple with a XA-1541. But none of my PC has a LPT port (only USB) and my 8050 disks wouldn't be readable cause IEEE-488.

So I took an Atmega32 and made the XS-1541 to connect my drives to my USB port.


After this the Commodore fever was burning hard. At eBay I got a VIC-20 and I was inspired to make Final Expansion 3.


Now I'm working on a 1541 floppy speeder (200 times) - David-65.

---

But bakc to ontopic ...

Maybe you can patch Maverick to run with your CMD drives? Are ROM listings of the DOS available for CMD drives?