|
| |
|
Netdrive For Linux/Unix [2009] |
AKA :
Netdrive
| User rating: | awaiting 8 votes (8 left) |
Credits :
No credits found
Download :
Look for downloads on external sites:
Pokefinder.org
User Comment
Submitted by 6R6 on 2 October 2009
| Sorry, I ment SDIv20b8. I updated it when talking to GT about supporting netdrive device number. |
User Comment
Submitted by neilbaldwin on 2 October 2009
Greg,
I tried the DOS commands and it seems only "$" works with any reliability :(
I'll look into what gets sent from C64->netdrive but I don't hold much hope of making them work. It does say in the original netdrive that the functionality is very limited.
Oh, and I tried the latest SDI2B7 but you cannot select device 6 as you described. Is there a newer version (I got it from your website)?
|
User Comment
Submitted by 6R6 on 1 October 2009
Sounds cool, I havent tried Netdrive myself. But GT told me it worked for him. I updated SDI 20b7 to work with CTRL+6 (to select device number 6).
Which means you now can select device numbers 6-15 from the load menu in SDI.
And did you try if the SDI doscommand window works ?
You can access that window from loadmenu - by pressing shift+spacebar.
It can be used to make, delete, and browse directories.
And ofcourse delete and rename files.
|
User Comment
Submitted by neilbaldwin on 1 October 2009
Uploaded a new version.
This version stops "file extensions" .PRG, .SEQ and .USR from being automatically added to files.
This does mean that you have to specify the full name e.g. LOAD"DEMO.PRG",6,1 but it does fix the issue I described where some programs would cause netdrive to add and extension to recognised file types resulting in error.
I also added a fake disc name (generated from the current folder/directory on the host machine) which helps programs that (rightly) ignore the first directory entry.
Both of these were done specifically to help me use netdrive with SDI. If anyone spots any adverse affects let me know.
|
User Comment
Submitted by neilbaldwin on 1 October 2009
I've found the source of the problem. It's to do with how the unix path/file name is constructed from the file name that is sent from the C64. The code appends common extensions such as .PRG and .SEQ which is OK from Basic as you can just do, say, LOAD"DEMO",6 and it will automatically look for "DEMO.PRG". However, if you're trying to load from within a C64 program that specifies the whole name, say, "DEMO.PRG", the file that it tries to load at the PC end is "DEMO.PRG.PRG" and fails.
It was pretty easy to find and prevent this but I want to test it some more.
The other issue is that unlike a real C64 disc or a .D64 image, when you get a directory listing from the PC the first line (that contains the disc name on C64) is missing so in some C64 programs the first entry is missing because it's assumed to be the disc name.
You can get around this by putting a dummy file in the folder but I'm going to look at parsing a faked disc name to send to the 64 before the folder contents are fetched.
|
User Comment
Submitted by neilbaldwin on 30 September 2009
Hmmmm. Couple of issues with the linux patch, at least when trying to use it via SDI.
If you try to load or save in SDI you get a "File not found" error (62) despite the file showing up in the directory listing.
However, if I run the Windows version of netdrive (in Parallels Desktop) it works fine.
Seems to load/save files from Basic though.
I'll see if I can track down the problem.
|
User Comment
Submitted by Hermit on 29 September 2009
Great that Linux users are also supported, I'm surely trying this on my Puppy Linux...
(if there were also a HardSID-4U driver for Linux...:)
|
User Comment
Submitted by neilbaldwin on 29 September 2009
Just added a new version. I forgot to include the makefile.
|
User Comment
Submitted by FMan on 29 September 2009
Hmm. Cool! I'll give it a try on Ubuntu.
|
|
|
|
 | Search CSDb |
|
| Navigate | |
|
| Detailed Info | |
|
| Fun Stuff | |
· Goofs
· Hidden Parts
· Trivia
|
|
| Forum | |
|
| Support CSDb | |
|
 |  |
|
