|
Post by 1570 on Nov 18, 2007 6:27:36 GMT -5
Sure. I did. Concerning mouse, it is possible to attach a 1351 mouse (either an original one or a hardware-level emulation, see [1]). Writing a driver for your mouse interface project [2] might be possible too but timing will be tricky. In any case I don't have GEOS programming knowledge. Perhaps expertsetup can shed a bit of light on the tools he used for the userport joystick driver. Then, patching CONFIGURE properly to support DTV DMA might also be possible (currently that's done in-memory only and then freezed which is probably not the proper way to go ). [1] www.zimmers.net/anonftp/pub/cbm/documents/projects/interfaces/mouse/Mouse.html[2] galaxy22.dyndns.org/dtv/common/ps2mouse/index.html
|
|
|
Post by 1570 on Nov 19, 2007 12:12:39 GMT -5
Concerning mouse, it is possible to attach a 1351 mouse As noticed by Unseen in Forum64, this can't be done since the 1351 uses analog PotX/PotY lines that are not available on the C64DTV/Hummer.
|
|
|
Post by pyrofer on Nov 19, 2007 16:50:39 GMT -5
I recently wrote the PS/2 mouse protocol on a PIC, it would be easy to output the mouse packets in any form required for the DTV from there. I know its not the same when you need a hardware interface but any use?
|
|
|
Post by 1570 on Nov 19, 2007 17:11:16 GMT -5
Thanks for the offer. I already found some code for that in the net. A microcontroller would allow a mouse on a joyport certainly. Directly attaching a PS/2 mouse will probably not be possible since then it'd interfere with keyscan (either because of it pulling lines to GND, looking like joystick movement and scrambling keyscan, or by getting confused because of the keyscan routine pulling lines to GND). With a microcontroller it's possible to have the mouse transmit only after sending some kind of special request. However, I probably won't implement that, and for the two people in the world really being interested in a GEOS mouse on the DTV probably going the userport way is quite a lot simpler .
|
|
|
Post by 1570 on Nov 23, 2007 20:54:49 GMT -5
|
|
|
Post by cyberdyne on Sept 11, 2008 8:37:23 GMT -5
Let's reactivate this thread!
What about the PS2 mouse driver for GEOS? This and a new filesystem driver to use an SD2IEC/MMC2IEC insted the 1541 would be perfect.
|
|
|
Post by David Murray on Sept 11, 2008 9:51:55 GMT -5
Let's reactivate this thread! What about the PS2 mouse driver for GEOS? This and a new filesystem driver to use an SD2IEC/MMC2IEC insted the 1541 would be perfect. I admit it would be a cool achievement, it would also be a lot of work. And the thing that comes to mind with GEOS, at least for me, is that I would boot it up, play with it about 5 minutes, think to myself, "this is neat." then get bored, then never use it again. After all, what useful things are there to do in GEOS these days? I used to use GEOWrite for doing my school papers in highschool, but today I'd much rather use OpenOffice for a task like that. Not to mention, I wouldn't want to print it on a dot-matrix printer.
|
|
|
Post by robertb on Sept 11, 2008 11:26:41 GMT -5
After all, what useful things are there to do in GEOS these days? Same as in the past -- write documents, keep records, calculate with spreadsheet, make graphics, publish newsletters, send faxes, play GEOS games, listen to SID music, dearchive/archive files, etc.. I used to use GEOWrite for doing my school papers in highschool, but today I'd much rather use OpenOffice for a task like that. It's the OpenOffice for Commodore 64/128s. Not to mention, I wouldn't want to print it on a dot-matrix printer. With GEOS/Wheels, I print my files with a Postscript II ink-jet printer (gotta get that Postscript II laser printer going). Truly, Robert Bernardo Fresno Commodore User Group videocam.net.au/fcug
|
|
|
Post by David Murray on Sept 11, 2008 16:40:41 GMT -5
Robert, you are probably the only person left that writes their documents, spreadsheets, newsletters, etc... in GEOS. I don't know.. To me, that would be like choosing to ride a bicyclce without a seat, when another bicycle with a seat is available.
|
|
|
Post by robertb on Sept 11, 2008 20:18:42 GMT -5
Robert, you are probably the only person left that writes their documents, spreadsheets, newsletters, etc... in GEOS. Bruce Thomas of CUE, Dave "Lord Ronin" Mohr of ACUG, the GEOClub that shows up at every bi-monthly Commodore Show in the Netherlands... To me, that would be like choosing to ride a bicyclce without a seat... You've been watching too many Benny Hill comedy skits! ...when another bicycle with a seat is available. My classic Raleigh bicycle has a seat just like the new bicycles. Sometimes, classic bicycles are even worth more than new, equivalent ones. Truly, Robert Bernardo Fresno Commodore User Group videocam.net.au/fcugThe Other Group of Amigoids www.calweb.com/~rabel1/
|
|
|
Post by 1570 on Sept 12, 2008 5:02:06 GMT -5
What about the PS2 mouse driver for GEOS? This and a new filesystem driver to use an SD2IEC/MMC2IEC insted the 1541 would be perfect. I admit it would be a cool achievement, it would also be a lot of work. The PS2-mouse-on-userport driver is just a matter of creating a GEOS driver from nojoopa's existing code. With VICEplus already providing PS2 userport mouse emulation I think this can be done quite quickly. A driver for sd2iec already exists but with 160k d64 images in sd2iec this is pointless - d81 support in sd2iec is in the works though. Creating 'real' (non-image) GEOS support in sd2iec would be a lot of work indeed. I wouldn't know how to start anyways as the GEOS floppy drive 'API' is not really suited for this, working on a track/sector (not file) basis. If anyone wants to work on this, just ask; I can give further pointers. Starting x64dtv and hacking away in its monitor is not such a big problem really.
|
|
|
Post by Unseen on Sept 12, 2008 7:25:42 GMT -5
d81 support in sd2iec is in the works though. It's working and available in the git repository, but not in any release version yet.
|
|