CBM4WIN Printer Port Problem
in [Commodore]
|
From: KilrPilr on 3 Feb 2007 13:01 "Spiro Trikaliotis" <news-200605(a)trikaliotis.net> wrote in message news:slrnes6th3.at8.news-200605(a)news.trikaliotis.net... > > I have got some offerings for hardware. I have even kept some hardware > parts, but so far, everything I kept was kept because someone told me to > keep it, to use it as a permanent donation. I never kept anything I was > not told to keep, and I want to keep it that way. > > Note, Womo and I, we know each other a little bit, as we have worked > together for some time now. Also, we have meet in real life. We speak > very openly to each other, and we make jokes every now and then. Thus, I > think you have to take our words for each other with a pinch of salt. > > Regards, > Spiro. > Hey Spiro, No problem. I figured it was just a misunderstanding on my part. My offer still stands though, so long as you can find time to do it in the relative near future. I understand if you dont have time. I just think adding this functionality to cbm4win would be excellent and is very needed. When I find time, I will try to do the commands to test the program with my cmd hd. Leo
From: KilrPilr on 3 Feb 2007 13:36 "Wolfgang Moser" <wn0612(a)d81.de.invalid> wrote in message news:epth4u$qm5$1(a)vs5413.trikaliotis.net... > oh my god, there you got me wrong. > > It was in no way my intention to say that Spiro would > not do improve support for CMD's devices. It is more > that I know that he is a very busy man, overloaded > with work. In such a situation it could be considered > not the best behaviour to call for more work to do. > But he did, maybe because he didn't expect that > someone would _really_ give away his expensive CMD > device for some weeks or months. I figured as much but thought I would throw that out there to see what was up. I guess im just paranoid these days.Yeah im sure he didnt think someone would donate hardware, but im just that needy! I really want to see support for CMD hd's and im willing to put my HD on the table to get it done. Unfortunately I have no experience in programming or anything so I depend on others for adding functionality that i think would be beneficial. I am surprised that some others arent standing forward to try to help out. I guess these other people have a quick efficient method of transferring data from a cmd hd to a pc. > > I did lend Spiro two different PCI LPT port cards to > help him improving support for such PCI LPT cards. > Unfortunately there is some serious issue with such > PCI LPT port cards in not generating the needed IRQ, > so that OpenCBM is not able to work with these, but > mainboard integrated LPT ports only. > And Spiro and I already did invest 200 hours, if not > more in searching for a solution and trying these > out (implementing, testing, making educated guesses > about the failure reason, ...), with not having had > the luck to find a solution. Unreal! As I use a pci dual lpt card in my computer as I somehow messed up my onboard one hot swapping the plug . seems to work fine. I havent had any wierd errors or happenings. > > That's why I said that it would be not a good idea > to mention that /other/ donation. It _did_ already > cost toooo much work and still isn't fixed yet, nor > do we have got an idea how a solution could be done. > Currently the workload is at my side, I would have > to some tests with unixoide systems, if IRQs from > PCI LPT port cards can be handled with cbm4linux > there. If this does work, we would know that it > would be no hardware issue, but either an OS, > driver, or otherwise software related thing. Gotcha. :) Maybe it is a driver problem as my pci lpt card seems to work fine. > > > Leo, are you sure that CMD devices are not > supported by OpenCBM currently? Well all i did was hook up my cmd hd with my xap cable (without using the parallel part of course) as if it were a 1541 and try to copy files. while the directory loaded and everything seemed good, as soon as I went to copy a selected file, it errored right away.The error is "{warning} error reading myfile ". This was with the options set to Auto detect serial or parallel. I then changed it to serial (original slow mode) and when i try to copy a file in that mode, it errors with, "[fatal} unknown transfer mode: original " I then tried to do a .d64 of the partition and while it pretended to work, non of the hd lights were flashing or on so I knew it was just stalled. If I auto detect what drive it is, it says "8: unknown" >Did you play with > the most basic commands of cbmctrl yet? No, I really dont know what im doing when it comes to dos commands. I can give what u wrote here a try but if it isnt word for word or letter for letter I probably wont get it right. Ill try it though >I mean, > did you try out to read some blocks from the CMD > the crude hard way, to only see, if something can > be transferred. Something like: > > > cbmctrl status 10 > > cbmctrl command 10 "any well known CMD disk drive command" > > cbmctrl lock > cbmctrl open 10 2 "MyFile" > cbmctrl talk > cbmctrl read "ToMyLocalFile.bin" > cbmctrl untalk > cbmctrl close > cbmctrl unlock > > If such basics do work, then there is nothing more > to do than writing some shell scripts that send > commands to the drive (changing subdirectories), > listing the files, filling that into a foreach loop > and transferring each single file with basic IEC > transfers. Ill give it a try. > > All the higher level transfer tools will not work > with CMD hardware in most cases _by_design_. These > were made for the Commodore 1541 floppy disk drive > and its compatibles (1540, 1570, 1571) to deliver > mainstream usability to the masses with a minimum > effort. That's one of the principles, where > OpenSource is well working at from scratch. > > > Womo But I thought cmd devices were the most compatible to commodore equipment so then should theoretically work as if it was a C= drive. I guess in very basic scenarios, they are, but not in more technical cases which this obviously is. Oh man, i can see a future where cbm4win supports cmd hd's and from within the gui a user will be able to switch partitions within his cmd hd with the click of a button and transfer out the contents of that drive to a pc with just a few mouse clicks. Cant wait! :) Leo
From: KilrPilr on 3 Feb 2007 14:13 Hi Womo, ok here is a copy of the text i used to get the status on the HD. It seems random until I reset the drive .Then I received the proper dos status. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Athlon64>f: F:\>cd F:\opencbm-0.4.0-i386\exe F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 4 F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 H F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 P F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 @ F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 .. F:\opencbm-0.4.0-i386\exe>cbmctrl reset F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 73,cmd hd dos v1.68,00,00 F:\opencbm-0.4.0-i386\exe> I tried the other commands u gave me but nothing happened. I dont know if I am entering them correctly or not and I dont normally work with the command channel in commodore dos so I dont know a decent command to input to get a directory or open a file. Sorry. Im still a newb when it comes to using the command channel.If you can be more specific as to what to type, including spaces and such, It would be no problem. Just dont expect that I will know something that may be obvious to others. Leo
From: Wolfgang Moser on 3 Feb 2007 16:27 Hello Leo, KilrPilr schrieb: > > Unfortunately I have no experience in programming or anything so I depend on > others for adding functionality that i think would be beneficial. I am hopefully there are anybody else out there... We will see why shortly. >> Unfortunately there is some serious issue with such >> PCI LPT port cards in not generating the needed IRQ, >> so that OpenCBM is not able to work with these, but >> mainboard integrated LPT ports only. > > Unreal! As I use a pci dual lpt card in my computer as I somehow messed up > my onboard one hot swapping the plug . seems to work fine. I havent had any > wierd errors or happenings. _This_ is good news. Please tell us the name of your card, its manufacturer and all else you can tell. > Gotcha. :) Maybe it is a driver problem as my pci lpt card seems to work > fine. Maybe your card came with an exceptionally well written driver that fully supports of of the nuts and bolts needed by Windows' parport.sys. >> Leo, are you sure that CMD devices are not >> supported by OpenCBM currently? > > Well all i did was hook up my cmd hd with my xap cable (without using the > parallel part of course) as if it were a 1541 and try to copy files. But a HD is no 1541, therefore the tools cbmcopy as well as d64copy cannot be used. This mostly is a hardware issue since both tools need to upload custom code into the drive to pull out a notable speed improvement through custom serial protocols. > while the directory loaded and everything seemed good, as soon as I went to > copy a selected file, it errored right away.The error is "{warning} error This definetly proofs that CMDs device __basically__ are already support by OpenCBM. With this I mean that the OpenCBM driver stack does support the IEC protocol in a way that is compatible to CMDs device. All you need are some tools that do a similar thing to cbmcopy, but in very native IEC transfer mode. Developing a custom speeder protocols especially for CMDs device is far beyond the current scope of all of our project targets since there much more things with a higher priority. > reading myfile ". This was with the options set to Auto detect serial or > parallel. I then changed it to serial (original slow mode) and when i try to > copy a file in that mode, it errors with, "[fatal} unknown transfer mode: > original " Yes, that's true. Since standard IEC file transfers can be done with the basic tool: cbmctrl and some of the custom commands I told you in my previous mail, there was no need (for the original cbm4linux developer Michael Klein) to do the same in cbmcopy. That tools was specialised in single file transfers with custom protocols that definetly don't work with CMD devices for hardware incompatibility reasons, regardless how "compatible" these devices are told. If they would be as compatible as needed by the custom protocols, it would morph into a 1541 clone with 1541 hardware instead of beeing a HD. > I then tried to do a .d64 of the partition and while it pretended to work, > non of the hd lights were flashing or on so I knew it was just stalled. Hmmmmm.... in this mode of your CMD HD, you __should__ do a test with d64copy in original transfer mode, so please tell us what happens if you do: 1) switch CMD HD into 1541 partition mode and into 1541 compatibilty mode 2) d64copy that partition with: d64copy -to -vvv -i1 -B -d0 8 yourpartitioncopy.d64 And be prepared that this could need half an hour or so, although BAM copy mode should do a good job in decreasing that time. > If I auto detect what drive it is, it says "8: unknown" Nice... well, this would be a point that could be improved a bit somewhere in the driver, but I'm still arguing with Spiro about architectural concepts. >> Did you play with >> the most basic commands of cbmctrl yet? > > No, I really dont know what im doing when it comes to dos commands. > I can give what u wrote here a try but if it isnt word for word or letter > for letter > I probably wont get it right. Ill try it though Hmmm I thought that you got some experiences with you CMD HD from programming it from within BASIC V2 (C64) or V7 (C128). With that it would be not difficult to write some little scripts. Perhaps we found another solution with d64copy and CMD 1541 paritions. > But I thought cmd devices were the most compatible to commodore equipment so > then should theoretically work as if it was a C= drive. I guess in very > basic scenarios, they are, but not in more technical cases which this > obviously is. CMD's device in fact are very compatible up to some decent limit. The custom protocols used in cbmcopy as well as d64copy require a much more deeper compatibility down to the hardware level. As I said above, you surely don't want your HD beeing converted into a 1541 disk with all its limitations. That is not the reason you bought a HD for. > Oh man, i can see a future where cbm4win supports cmd hd's and from within > the gui a user will be able to switch partitions within his cmd hd with the Payton may want to add support for some CMD DOS commands into the GUI. Since the GUI operates (mostly) on top of the tools there is nothing more to do than sending some of the cbmctrl command presented in my previous mail to cbmctrl in a more programmatic way. Sure, you need to know which commands the CMD HD supports. Maybe you get asked to install some SSH server onto your machine, so that someone else can log in to your machine and then playing around with your CMD HD over the internet? No need to air mail it oversea and back. > click of a button and transfer out the contents of that drive to a pc with > just a few mouse clicks. Cant wait! :) Well, _waiting_ is the very first thing that comes to my mind, when I think on CMD's HD and the serial X cables. Womo
From: Wolfgang Moser on 3 Feb 2007 16:49
Hi Leo, KilrPilr schrieb: > Hi Womo, > ok here is a copy of the text i used to get the status on the HD. It seems > random until I reset the drive .Then I received the proper dos status. > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > > C:\Documents and Settings\Athlon64>f: > > F:\>cd F:\opencbm-0.4.0-i386\exe > > F:\opencbm-0.4.0-i386\exe>cbmctrl status 8 > 4 this looks not too bad. Maybe your drive was irritated from my series of commands. These were not adequate, but were meant to describe a raw idea of how things do work out with cbmctrl. Here is a sequence that I just did test with my 1571 disk drive (at address 9) on a given file: cbmctrl dir 9 Shows the directory, so that I can see which file to select. cbmctrl lock Lock the driver so that no other tool can interrupt the current session, recommended for script use. cbmctrl -p open 9 2 "c64 dolphindos2" Use PETSCII translation (-p) so that I don't need to change all chars to uppercase myself. Then open a channel for drive 9 at the drive's logical transport channel 2 (it can handle several ones simultanously) with the given filename. That one was looked up from the dir command before. cbmctrl talk 9 2 Let the drive start sending the contents of that file. cbmctrl read localfile.prg Let cbmctrl receive these contents and store them into the file with name: localfile.prg cbmctrl untalk After the transfer is finished tear down the transfer logically. cbmctrl close 9 2 Close the logical channel within the drive. cbmctrl lock Since we don't want to somethigng else, unlock the driver's session. Replace each "9" with an "8" and this sequence should work with your HD on a similar file. > I tried the other commands u gave me but nothing happened. I dont know if I > am entering them correctly or not and I dont normally work with the command > channel in commodore dos so I dont know a decent command to input to get a > directory or open a file. Sorry. It is me who needs to sorry about giving you and untested command sequence. It seems that I overestimated your DOS (CBM/CMD devices) command level skills. I thought it would be anough to give you some hints and you would learn the rest by reading cbmctrl's manual page: http://opencbm.trikaliotis.net/opencbm-13.html I spend a lot of time on rewriting big parts of that page, so please give it a read ;-) > Im still a newb when it comes to using the > command channel.If you can be more specific as to what to type, including > spaces and such, It would be no problem. Just dont expect that I will know > something that may be obvious to others. Bye, bye and hopefully you get some success with transferring your files. Womo |