opencbm-announce Mailing List for OpenCBM
Brought to you by:
strik
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Spiro T. <cb...@tr...> - 2022-01-23 20:42:31
|
Hello, I just uploaded a Windows binary of OpenCBM 0.4.99.104. The biggest and most notable change is the fix for the Windows installer. With v0.4.99.103, the update did not work, only a new install. With v0.4.99.104, this should be fixed IF THE DEVICE IS PLUGGED IN WHILE INSTALLING THE DRIVER! In order to use 0.4.99.104, just download it, unpack it and run install.cmd with your normal user account! It will automatically elevate ("UAC") in order to get the rights! Hint: You can use your normal user account for installation. The script will ask for the necessary rights as soon as it is needed. Hint: For now, I tested it on Windows 7 and 10. It requires the Powershell, so everything after Windows 7 SP1 should work. It can be found here: https://spiro.trikaliotis.net/download/opencbm-0.4.99.104/opencbm-0.4.99.104.zip While installing the USB drivers, a red alert will pop up that tells you that we are not signed, and what bad things can happen. I cannot do anything about it as I cannot sign the binary myself. So, If you do not trust me, do not install OpenCBM! Possible problems: ================== 0. You get a red alert (sorry, I only have the German text) (cf. attachment): "Windows Security Der Herausgeber der Treibersoftware konnte nicht überprüft werden. (Could not determine the manufacturer of the driver software) --> Diese Treibersoftware nicht installieren (--> Do not install this driver software) [...] --> Diese Treibersoftware trotzdem installieren (--> Install this driver software anyway)" This is not a problem. I cannot sign the software, so Windows insists on this popup. If you trust me, use option 2 ("install anyway"). If not, you cannot use OpenCBM. 1. After installation of the driver and trying to perform an OpenCBM command (cbmctrl, ...), you get the message: Error loading plugin '(null)': The parameter is incorrect. (87) Error loading plugin '(null)': The parameter is incorrect. (87) NO PLUGIN DRIVER!: The parameter is incorrect. It seems the installation was not done correctly. Did you get an UAC prompt when trying to install OpenCBM? Please note that an administrator account is not enough, you need the UAC prompt (unless it is disabled by you, of course). It is also possible that you did not install OpenCBM at all. It needs an installation, or it will not work. Please use the install.cmd script, as described above. Changes w.r.t. 0.4.99.103: ========================== * new: xum1541cfg: add bootloader command * new: cbmctrl add low-level IEC line handling (ireset, uireset, atn, uatn, data, udata) * new: xum1541 firmware version 8 for PROMICRO boards with various fixes and additions (SRQ nibbling, bootloader) * new: xum1541 firmware split into supported and unsupported devices; new make target "unsupported" * new: xum1541 firmware and plugin: include compilation details * new: xu1541 firmware: Generated combined bootloader and firmware hex files for easier initial setup * fix: Windows installation could not update the installed driver for xu1541 or xum1541 devices. Fixed, update works now. * fix: xum1541 firmware: fix IEC_SRQ setting/unsetting which resulted in unpredictable behaviour * change: cbmcopy: don't filter user-provided local output filenames * change: Various fixes for newer compilers (gcc) and platforms (Linux 5.x) * change: change devmodel for parport driver to allow compilation with newer versions (Linux) * change: do not build plugins that are not needed What is still missing for v0.5.0? ================================= - For Windows XP and 2000, the drivers must be provided so xum1541 and xu1541 can be installed there. - excessive testing - documentation updates Regards, Spiro. -- Spiro R. Trikaliotis http://spiro.trikaliotis.net/ |
From: Spiro T. <cb...@tr...> - 2007-11-11 19:03:46
|
Hello, I just released OpenCBM 0.4.1. This is mainly a bugfix release. It does not include any new features; instead, all patches which fix compilation issues and some (small) IEC protocol errors are included, only. I wanted to release a much more featured version, but this is delayed because of time constraints from my side. Thus, I decided to release a minor change, so people do not have to apply patches by hand to compile OpenCBM for Linux. As always, OpenCBM can be found on its SF page: http://sf.net/projects/opencbm Regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |
From: Spiro T. <cb...@tr...> - 2006-06-21 08:08:49
|
Sorry for the test. Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://opencbm.sf.net/ |
From: Spiro T. <cb...@tr...> - 2006-06-21 07:56:25
|
Hello, the mailing address of this list has changed. It is now: ope...@li... Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://opencbm.sf.net/ |
From: Spiro T. <cb...@tr...> - 2006-06-10 17:39:30
|
I am forwaring the following announcement from Wolfgang: ----- start forwarded message: ----- A couple of weeks ago Spiro announced OpenCBM 0.4.0. If you're using Windows 2000 or XP and are tired of rebooting to DOS to use Star Commander for reading/writing Commodore disks, definitely check out OpenCBM and its subproject cbm4win. http://opencbm.sf.net/ Gui4cbm4win is a small VisualBasic 6 application that lets you transfer individual files or real D64 images to/from Commodore disks. It also provides buttons to identify your drives upon installation and do useful jobs like formatting disks. Please take note of a license change. While Leif's original source version 0.09 was distributed as Public Domain software, I put the updated version of Gui4cbm4win under the zlib/libpng license model. I felt that there was some need to clearly define usage and reusage by further developers. I wanted to make a crystal clear definition of this branch (version 0.40 and up) of Leif's software beeing OpenSource for now and all times without the copyleft restriction of the GNU General Public License, but still beeing compatible to the GPL. Finally I wanted to allow distribution via Sourceforge. All in all I hope to preserve the will of Leif as much as possible with that license model. The updated version of Gui4cbm4win can be downloaded from here: http://sourceforge.net/project/showfiles.php?group_id=122047 Just extract the binary archive and put the gui4cbm4winexe file into your cbm4win\exe directory and start it from there. Read the file changelog.txt for a detailed view onto the changes and additions as well as a few fixes made to Leif's version. Leif's old web page with further explanations, features and limitations is still available, but was not and does not get updated anymore: http://www.jammingsignal.com/gui4cbm4win/ At least, please note that I did not take over Leif's project officially. I only did the accomodations the let Gui4cbm4win communicate to OpenCBM 0.4.0 again since no one else did or told the OpenCBM team to do so. Therefore please don't expect any further updates or bigger additions of functionality to Gui4cbm4win. The sooner I get VisualBasic 6 uninstalled from my system again, the happier I'll be ;-) Womo ----- end forwarded message ----- Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://opencbm.sf.net/ |
From: Spiro T. <cb...@tr...> - 2005-05-30 17:24:40
|
Hello, I'm proud to announce the availability of cbm4win, version 0.1.0a (BUGFIX release). What is new? This version fixes some errors. Some of them are SECURITY ISSUES, thus, I highly recommend upgrading to that version. Furthermore, d64copy wrote d64 files which were "wrong" if there were errors on the disk. Another issue is a fixed performance problems, which occurred especially with multiprocessor machines (SMP) or Hyperthreading machines (HT), but also with NT4. The fixes in more detail: * drivers (cbm4wdm.sys/cbm4nt.sys): o performance fix for some machines, especially SMP, HT, and NT4. o Allow for specifying the cable type via the registry (instead of auto-detecting). * cbmctrl: o Fixed 2 format string vulnerabilities o Do not allocate a 64KB buffer on the stack anymore which might allow for a stack overflow. * instcbm: o Do not allocate a 128KB buffer on the stack anymore which might allow for a stack overflow. o Fixed 3 "off-by-one" buffer accesses, resulting in access to non-allocated memory. o Fixed some more possible accesses to uninitialized variable. * d64copy: o Make sure image is correctly closed when aborted with Ctrl+C. o When writing error codes into a file (for d64 with error map), make sure the jobcode is written ($01-$0F) instead of the DOS error code (18 and higher). * cbmcopy: o Fixed rare shutdown problem. * cbmformat: o New drive routine with probing. * all: o a misplaced if() statement could lead to access of uninitialized variable space. Fixed that. o Error in debugging output could result in multiple evaluations of some functions. Fixed that. What is cbm4win? cbm4win is a port of cbm4linux [1] to Windows. It allows for access to a VIC 1540, 1541, 1570, 1571, or even 1581 floppy drive from the PC on Windows NT, 2000 and XP. Which operating systems are supported? Currently, there is support for Windows NT 4.0, Windows 2000, Windows XP, and Windows 2003 Server. Previous versions of NT have not been tested, but they might work, too. Is Windows 95, 98 or Me supported? No, there is currently no support for these Windows versions. Anyway, support for Windows 98 Second Edition and Me is planned. I do not know if it will be possible to port it to Windows 98 First Edition, though. What can I do with cbm4win? The most important things you can do is to copy D64 or D71 images from a real drive to the PC, or from the PC to a real drive with the help of d64copy. Furthermore, you can copy single files in both directions, too. Some more tools (for example, cbmctrl) are given, too. Is there 3rd party support for cbm4win? VICE [2] will have support for cbm4win in the next version. There is an internal version of YAPE [3] which supports cbm4win, too. Other people have already showed interest in supporting cbm4win in their products, too. What is the development state of cbm4win? This is the first public announcement of cbm4win. Because of this, there is high probability that there are still errors. What hardware is needed in order to use cbm4win? Of course, you need a PC running Windows NT, 2000, XP, or 2003. Furthermore, you need a real drive, like the VIC 1540, 1541, 1570, 1571, or 1581 (1581 not fully supported). Then, you need an XA1541, XM1541, XAP1541 or XMP1541 cable in order to connect the driver with the PC. Acknowledgements and Thanks Cbm4win is heavily based on cbm4linux [1], written by Michael Klein. Cbm4linux itself uses work from Star Commander [4], written by KOVÁCS Balázs a.k.a. "Joe Forster". I like to thank both for their steady help and their patience. Furthermore, I want to thank the following people: - Michael Klein for cbm4linux and many discussions. I do not know if I would have started this project without this. - KOVÁCS Balázs a.k.a. "Joe Forster" for Star Commander, his advice, and for giving me cables for free to work on this project; - Wolfgang Moser for steady discussions, testing, and bug reports, as well as giving me some more needed equipment; - all of my testers for steady tests, reports, and discussions. Contact, Download, Further Info: cbm4win can be found and downloaded at http://www.trikaliotis.net/cbm4win [5] Furthermore, I have setup a project page on sourceforge: http://sf.net/projects/cbm4win/ [6] If you want to submit bug reports, I would thank you for submitting to the bug tracking system [7] over there. There are even two mailing lists available for announcements [8] and for user discussions [9]. If you want to contact me directly, just contact me at cb...@tr..., or go to my homepage at http://www.trikaliotis.net/. Any hints, suggestions, and the like are welcome! Happy transferring, Spiro. [1] http://www.lb.shuttle.de/puffin/cbm4linux/ [2] http://www.viceteam.org/ [3] http://yape.plus4.net/ [4] http://sta.c64.org/sc.html [5] http://cbm4win.sf.net/ [6] http://sf.net/projects/cbm4win/ [7] http://sf.net/tracker/?group_id=122047&atid=692219 [8] http://lists.sourceforge.net/lists/listinfo/cbm4win-announce [9] http://lists.sourceforge.net/lists/listinfo/cbm4win-user Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ |
From: Spiro T. <cb...@tr...> - 2004-11-28 16:21:26
|
Hello, I'm proud to announce the availability of cbm4win, version 0.1.0 (first public release). What is cbm4win? cbm4win is a port of cbm4linux [1] to Windows. It allows for access to a VIC 1540, 1541, 1570, 1571, or even 1581 floppy drive from the PC on Windows NT, 2000 and XP. Which operating systems are supported? Currently, there is support for Windows NT 4.0, Windows 2000, Windows XP, and Windows 2003 Server. Previous versions of NT have not been tested, but they might work, too. Is Windows 95, 98 or Me supported? No, there is currently no support for these Windows versions. Anyway, support for Windows 98 Second Edition and Me is planned. I do not know if it will be possible to port it to Windows 98 First Edition, though. What can I do with cbm4win? The most important things you can do is to copy D64 or D71 images from a real drive to the PC, or from the PC to a real drive with the help of d64copy. Furthermore, you can copy single files in both directions, too. Some more tools (for example, cbmctrl) are given, too. Is there 3rd party support for cbm4win? VICE [2] will have support for cbm4win in the next version. There is an internal version of YAPE [3] which supports cbm4win, too. Other people have already showed interest in supporting cbm4win in their products, too. What is the development state of cbm4win? This is the first public announcement of cbm4win. Because of this, there is high probability that there are still errors. What hardware is needed in order to use cbm4win? Of course, you need a PC running Windows NT, 2000, XP, or 2003. Furthermore, you need a real drive, like the VIC 1540, 1541, 1570, 1571, or 1581 (1581 not fully supported). Then, you need an XA1541, XM1541, XAP1541 or XMP1541 cable in order to connect the driver with the PC. Acknowledgements and Thanks Cbm4win is heavily based on cbm4linux [1], written by Michael Klein. Cbm4linux itself uses work from Star Commander [4], written by KOVÁCS Balázs a.k.a. "Joe Forster". I like to thank both for their steady help and their patience. Furthermore, I want to thank the following people: - Michael Klein for cbm4linux and many discussions. I do not know if I would have started this project without this. - KOVÁCS Balázs a.k.a. "Joe Forster" for Star Commander, his advice, and for giving me cables for free to work on this project; - Wolfgang Moser for steady discussions, testing, and bug reports, as well as giving me some more needed equipment; - all of my testers for steady tests, reports, and discussions. Contact, Download, Further Info: cbm4win can be found and downloaded at http://www.trikaliotis.net/cbm4win [5] Furthermore, I have setup a project page on sourceforge: http://sf.net/projects/cbm4win/ [6] If you want to submit bug reports, I would thank you for submitting to the bug tracking system [7] over there. There are even two mailing lists available for announcements [8] and for user discussions [9]. If you want to contact me directly, just contact me at cb...@tr..., or go to my homepage at http://www.trikaliotis.net/. Any hints, suggestions, and the like are welcome! Happy transferring, Spiro. [1] http://www.lb.shuttle.de/puffin/cbm4linux/ [2] http://www.viceteam.org/ [3] http://yape.plus4.net/ [4] http://sta.c64.org/sc.html [5] http://www.trikaliotis.net/cbm4win [6] http://sf.net/projects/cbm4win/ [7] http://sf.net/tracker/?group_id=122047&atid=692219 [8] http://lists.sourceforge.net/lists/listinfo/cbm4win-announce [9] http://lists.sourceforge.net/lists/listinfo/cbm4win-user -- Spiro R. Trikaliotis http://www.trikaliotis.net/ |
From: Spiro T. <ml-...@tr...> - 2004-11-06 18:53:23
|
Hello list, after asking MagerValp if it is ok to do so, I want to announce the availability of cbm4win, version 0.11. What is cbm4win? cbm4win is a port of cbm4linux [1] to Windows. It allows for access to a VIC 1540, 1541, 1570, 1571, or even 1581 floppy drive from the PC on Windows NT, 2000 and XP. Is Windows 95, 98 or Me supported? No, there is currently no support for these Windows versions. Anyway, support for Windows 98 Second Edition and Me is planned. What can I do with cbm4win? The most important things you can do is to copy D64 or D71 images from a real drive to the PC, or from the PC to a real drive with the help of d64copy. Furthermore, you can copy single files in both directions, too. Some more tools (for example, cbmctrl) are given, too. Is there 3rd party support for cbm4win? VICE [2] will have support for cbm4win in the next version. There is an internal version of YAPE [3] which supports cbm4win, too. Other people have already showed interest in supporting cbm4win in their products, too. What is the development state of cbm4win? cbm4win is still in development. In fact, this is the first "almost" public announcement of it. I hope to get some valuable feedback before letting cbm4win out "in the wild". I use the cbm-hackers mailing list because I think here are the knowledgeable people and enthusiast which will help me find the biggest bugs. Although cbm4win has showed very stable in the past, I have to warn you: THIS DRIVER IS IN DEVELOPMENT! BECAUSE OF THIS, I DO NOT RECOMMEND TO USE IT! - USE AT YOUR OWN RISK! As this is a kernel-mode driver, malfunctioning can cause severe damage to your installed operating system and any application and/or data on it. Because of this, you should not use this driver without DOING A BACKUP BEFORE STARTING THIS DRIVER! What hardware is needed in order to use cbm4win? Of course, you need a PC running Windows NT, 2000, XP, or 2003. Furthermore, you need a real drive, like the VIC 1540, 1541, 1570, 1571, or 1581 (1581 not fully supported). Then, you need an XA1541, XM1541, XAP1541 or XMP1541 cable in order to connect the driver with the PC. Acknowledgements and Thanks Cbm4win is heavily based on cbm4linux [1], written by Michael Klein. Cbm4linux itself uses work from Star Commander [4], written by KOVÁCS Balázs a.k.a. "Joe Forster". I like to thank both for their steady help and their patience. Furthermore, I want to thank the following people: - Michael Klein for cbm4linux and many discussions. I do not know if I would have started this project without this. - KOVÁCS Balázs a.k.a. "Joe Forster" for Star Commander, his advice, and for giving me cables for free to work on this project; - Wolfgang Moser for steady discussions, testing, and bug reports, as well as giving me some more needed equipment; - all of my testers for steady tests, reports, and discussions. Contact, Download, Further Info: cbm4win can be found and downloaded at http://www.trikaliotis.net/cbm4win [5] PLEASE, DO NOT SPREAD THIS LINK (YET). I will wait for feedback from this announcement. If there is no critical bug, then I will announce it publically in the near future (most probably, next weekend). Furthermore, I have setup a project page on sourceforge [6]. If you want to submit bug reports, I would thank you for submitting to the bug tracking system [7] over there. There are even two mailing lists available for announcements [8] and for user discussions [9]. If you want to contact me directly, just contact me at cb...@tr..., or go to my homepage at http://www.trikaliotis.net/. Any hints, suggestions, and the like are welcome! Happy transferring, Spiro. [1] http://www.lb.shuttle.de/puffin/cbm4linux/ [2] http://www.viceteam.org/ [3] http://yape.plus4.net/ [4] http://sta.c64.org/sc.html [5] http://www.trikaliotis.net/cbm4win [6] http://sf.net/projects/cbm4win/ [7] http://sf.net/tracker/?group_id=122047&atid=692219 [8] http://lists.sourceforge.net/lists/listinfo/cbm4win-announce [9] http://lists.sourceforge.net/lists/listinfo/cbm4win-user -- Spiro R. Trikaliotis http://www.trikaliotis.net/ |
From: Spiro T. <cb...@tr...> - 2004-11-06 18:34:11
|
Hello, I just made the 0.11 version of cbm4win. As always, it can be found at http://www.trikaliotis.net/cbm4win Changes from 0.10: - instcbm now reports version information on --check and install. - cbmctrl, d64copy, cbmcopy now output error information if anything goes wrong. - DLL is loaded even if the driver is not installed. Problems are now determined if cbm_driver_open() fails. - "cbmctrl download" needs a specified filename now. Before, it output to stdout. Anyway, as Windows treats this is text mode, not binary mode, it was useless. - instcbm does not make use of the DLL anymore. - instcbm: The driver is stopped before a removal operaton. - Two different instances of some cbm4win programs cannot be started at the same time anymore. This prevents a lock up of the driver. - d64copy: If you copy a disc to an image which already exists, the error information was not removed from the file if necessary. This is fixed now. - instcbm: If the installation is removed, the DLL and driver files were not removed from the system directory. This is fixed. - libd64copy failed to recognize D71 images as valid images. Because of this, you could not write a D71 image back to a real floppy drive. Reported on the cbm4linux mailing list, patch by Michael Klein. I will announce this version to cbm-hackers, too! Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ |