According to the presentation that was given at ECCC, the ZoomFloppy will support nibbling with a stock 1571 over the IEC bus.  The guy did a pretty thorough presentation on the awesomeness of the 1571 when running in native 1571 mode.

After a lot of work and a few bug reports, the Release Candidate of CBM-Command Version 2.0 is now ready.  As a bonus, I've added a new feature: Disk Copying.  Now you can copy whole disks between like devices using CBM-Command!  Is it the fastest disk copier out there?  By no means, but having that feature at your finger tips is still useful. 


If there are no major bugs reported then this version will become the supported Version 2.0 release on January 21, 2011.


As always, you can download the current release at http://cbmcommand.codeplex.com


Thanks!
Payton Byrd

After some feedback and playing around with CBM-Command 2.0 Beta 1, I've identified and squashed the following bugs:


1) Timer for stats was slow
2) F1 was not showing help
3) Directory Navigation keys were wrong


All of these are now fixed.  Also, the new help file by popmilo, the winner of the documentation bounty, has been incorporated on the disk and is ready to be read!


Happy New Years for the CBM-Command Team!


http://cbmcommand.codeplex.com

OpenCBM works on Mac OS, as far as I know, but you're going to need an XU1541 or XUM1541 adapter since the Mac doesn't have a parallel port.  You may have to run OpenCBM under Windows on your Mac.

Greg King got the PET version of things working.  I don't have a distribution of the PET version of CBM-Command done (it doesn't fit on the CBM-Command D64 image), but you can build it yourself from the sources.  Alternatively, when I get some time I'll put together a D80 image with the PET version on it.

Well, if you're only interested in working with one string at a time then why even bother with any assembler to read the string?  My initial response was based on an assumption that you wanted to put each directory entry into a string, which I assumed meant you were keeping them all at once, which would indeed be a bad idea.

Quote from: stiggity on December 13, 2010, 02:37 AM
Anybody? Or if i open the directory channel, and perform an SYS, take each entry and store into a string? untill EOF??

I can tell you from experience that this is a BAD idea.  Large directories will VERY quickly eat up all your RAM.  For CBM-Command I had to limit my directory array and using a sliding window technique to display large directories.

Not trying to be a smartass, but that's not a 128D, that's a regular old flat 128.  Not that it's not valuable, just not RARE like a pristine 128D would be.

Release Notes
Major New Version

This is the first beta release of CBM-Command version 2.0. CBM-Command has undergone a lot of changes since version 1.7, most of which consist of a thorough cleaning of the code by Greg King and new features added by Payton Byrd with the space that Greg King freed up. Being the first public release after so many changes, please understand there will probably be some bugs.
New Features
* REL file copying between devices that support REL files.
* D71 disk image support - now you can create and write dual sided disk images with a 1571 drive
* Configurable Hot Keys - Don't like the default keys? You can redefine them yourself for version 2.0 using the Configuration program.

Changes
* Almost all code optimized for space savings to allow more features.
* Issuing a drive command is now done on the main screen instead of in a popup box
* When renaming a file, the directory remembers where you were so you don't have to scroll to the newly named file any longer.
* Changed disk image writes to reposition the buffer pointer in the drive instead of rolling the data in CBM-Command which freed up a buffer and some memory in the main program.
* Old keyboard shortcuts that required using the C= key now use the SHIFT key instead.

Known Issues
* Documentation is way out of date. New documentation is being written but is not yet ready for this release.
* Some of the default keys have changed. If you cannot find your old keyboard shortcut then go into the Configuration program and redefine the function as you need. These changes will be documented in the new version of the docs.

As always, you can download the latest version at http://cbmcommand.codeplex.com

Happy Thanksgiving!

See attached

One option you did not mention is working with Ingo and Jim Brain on implementing a fast serial routine on the uIEC that would be sufficient for your needs.  This may require a bounty on commodorebounty.com but in the end such a routine could be a benefit to the whole community and if the computer side uses standard kernel calls then it could become a cart or internal ROM.

If I remember correctly, the CBM2 machines were IEEE machines.  CBM-Command already has support in the code for the PET, but it doesn't work correctly on the pet because of some differences in CBM DOS on the IEEE drives (which I cannot identify).  I honestly don't have time right now to start on yet another version of CBM-Command, but the source code is available for anyone to pick it up and run with.

Quote from: Pinacolada on September 08, 2010, 01:11 PM
I vote for a customizable keytable. In some cases, my preferred shortcuts are different.

This is a good candidate for a Version 2.0 feature.

CBM-Command Version 1.7 has been released.  This version has several bug fixes but also includes real-time statistics on file copy and disk image operations.  There's also some visual goodness for 128 users.


http://cbmcommand.codeplex.com


Enjoy!

I'm going too.  I've got my hotel room and I've also gotten a table and presentation slot set up.

There is a major bug in the way that CBM-Command handles batches of file that are selected using the select all hotkey that can cause directory corruption.  Please discard any version older than 7/26/2010 (Version 1.6) and update to Version 1.6!


http://cbmcommand.codeplex.com

Quote from: stiggity on July 22, 2010, 05:03 AM
Payton:


What assembler did u use to write that??? Im not the best at ML and im finding it hard to navigate yer code.. sorry..

-Steve

It's written for ca65, which is the assembler portion of the cc65 library.

http://cbmcommand.codeplex.com


! Release Version 1.5 - Stable
This version encompases many enhancements and improvements of existing functionality, as well as inclusion of new target platforms (VIC 20, Plus 4) and features (D81 support, Configuration Color Picker).


! New Features
* (ALL) New color picker for the configuration program
* (64, 128, PLUS 4) 1581 Disk Image (D81) Support
* Added support for Commodore Plus 4 computer
* 32K Expanded VIC-20 now supported


! Changes
* (ALL) Removed CTRL key from hot keys that previously required it.  Hot keys the use the C= key still require it.
* (ALL) If you have 1 or more files selected (highlighted) and choose delete, all selected files will be deleted.  If you do not have any files selected (highlighted) then only the file that the selector is pointing to will be deleted.
* (ALL) When you rename a file the textbox is pre-populated with the name of the old file.
* (VIC 20, Plus 4) Configuration files are enabled and working correctly
* (ALL) Changed the UI for file transfers to use a new progress bar to give feedback on the copy operation.
* (64, 128, Plus 4) Changed the UI for disk image creation/writing to use a new progress bar to give feedback on the image operation.
* (VIC20) Refactored many of the screens to better fit the 22x23 layout. 
* (VIC20) Filename shortening removed and the file type moved to the left of the directory display
* (PLUS4) Created color scheme to match the environment
* (VIC20) Panels are not displayed side by side, only one panel is displayed at a time.
* (VIC20) D64 support is removed, the RAM was needed elsewhere.
* (ALL) The screen has been made more scalable.


! Known Issues
* None

For printing characters to the VDC directly you need to plot them directly into the appropriate screen memory location of the VDC RAM following the technique I used to copy data around in the VDC for CBM-Command.  Look at the code in this URL for guidance:


http://cbmcommand.codeplex.com/SourceControl/changeset/view/49966#829975

Honestly, it sounds like a memory leak in x128.exe that is causing your dynamic paging file to grow rapidly and then when you close the app then Windows correctly releases the memory which allows the paging file to shrink accordingly.


I would report this to the Vice Team.  They will know what to ask you to try to reproduce the problem where they can debug it.

http://cbmcommand.codeplex.com


Beta Release
This is the final beta release before version 1.5


New Features
* (VIC 20) Added support for the VIC 20 computer, requires 32K RAM Expander
* (PLUS 4) Added support for Commodore Plus 4 computer
* (ALL) New color picker for the configuration program
* (64, 128, PLUS 4) 1581 Disk Image (D81) Support


Changes
* (ALL) Removed CTRL key from hot keys that previously required it. Hot keys that use the C= key still require it.
* (ALL) If you have 1 or more files selected (highlighted) and choose delete, all selected files will be deleted. If you do not have any files selected (highlighted) then only the file that the selector is pointing to will be deleted.
* (ALL) When you rename a file the textbox is pre-populated with the name of the old file.
* (ALL) Changed the UI for file transfers to use a new progress bar to give feedback on the copy operation.
* (64, 128, Plus 4) Changed the UI for disk image creation/writing to use a new progress bar to give feedback on the image operation.
* (VIC20) Refactored many of the screens to better fit the 22x23 layout.
* (VIC20) Filename shortening removed and the file type moved to the left of the directory display
* (VIC20) Panels are not displayed side by side, only one panel is displayed at a time.
* (VIC20) D64 support is removed, the RAM was needed elsewhere.
* (ALL) The screen has been made more scalable.


Known Issues
* None

After a few productive days with CBM-Command we've reached another milestone.  D81 support is now baked into the versions of CBM-Command that do disk images (64, 128, Plus 4).  Also, the problems with reading/writing configuration files has been resolved in the Plus 4 and VIC 20 versions.


You can download the BETA at: http://cbmcommand.codeplex.com/releases/view/48724


Thanks,
Payton


PS.  There will be at least one more beta release after this one depending on what the resolution for the VIC-20 keyboard bug is.

Quote from: BigDumbDinosaur on June 25, 2010, 02:58 AM

Quote from: Payton Byrd on June 23, 2010, 11:31 AM
There aren't any kernel routines to save the screen.  There is no choice but to follow the procedure I used in CBM-Command.

You misunderstood me.  Of course, the screen kernel has no routines to save/restore portions of VRAM.  What I was saying is you are including primitives in your code that access the VDC hardware without regard for other activity that may be going on in the C-128.  Instead, take a look at the following subroutines in the screen kernel:

WRITE80   $CDCA    write to VRAM
WRITEREG  $CDCC    write to VDC register
READ80    $CDD8    read from VRAM
READREG   $CDDA    read from VDC register

Mapping the Commodore 128 gives a complete description on how to use these ROM routines to directly control the VDC.

Noted for future reference.

Quote from: BigDumbDinosaur on June 25, 2010, 02:58 AM
You might also want to consider using the 80 Column Display Manager, which does a lot of the grunt work for you in buffering and restoring screens.  Why reinvent the wheel?  80CDM does all of that work plus offers some extras you may find useful.

The reason I'm not using 80 column display manager, or any other 3rd party display manager for either 64 or 128 versions of CBM-Command is because there is a VERY STRONG NEED to standardize screen access to CONIO.H which allows the code to be shared across the two platforms without a billion #ifdef statements all over the place.

There aren't any kernel routines to save the screen.  There is no choice but to follow the procedure I used in CBM-Command.

I had to do this for CBM Command.  You should look at the source code for it:


http://cbmcommand.codeplex.com/SourceControl/changeset/view/47031#829975