Re: File Browser for uIEC

[silv...@wfmh.org.pl]

On 2013-01-10, at 22:43, Howlin' Alan wrote:

> Hi folks!
>
> I've written a file browser for the C64 and uIEC called NAV. It also works with the IDE64 and "real" Commodore drives. It uses 1351 mouse, joystick or keyboard, supports up to 5 drives.

It seems to have recognised six here ;-)

> Find out more and download at http://tinyurl.com/aeu32db

Nice! How does one change to parent dir?

--
SD!

[Howlin' Alan]

On Friday, January 11, 2013 7:58:40 PM UTC-5, silv...@wfmh.org.pl wrote:
> Nice! How does one change to parent dir?
>

When browsing a uIEC, there are parent and root options at the top of the disk directory.

[silv...@wfmh.org.pl]

I see - so only for uIEC. I couldn't find a way to navigate up on IDE64. Not sure about 1581 now.

--
SD!

[Berry de Jager]

@cd:[ArrowLeftKey]

See my blog: http://c64.berrydejager.com

Sent from my iBerry

--
You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To post to this group, send email to uIEC-...@googlegroups.com.
To unsubscribe from this group, send email to uIEC-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/uIEC-users/-/GpIN5Scno0UJ.
For more options, visit https://groups.google.com/groups/opt_out.

[Ingo Korb]

(probably in the wrong part of the discussion tree, but for some reason
I seem to be missing out on some of the messages on this list)

On 16 jan. 2013, at 13:47, Howlin' Alan <al...@bluesmanforhire.com> wrote:

> When browsing a uIEC, there are parent and root options at the top of
> the disk directory.

I guess it's time to kill that silly distinction in the identification
message - file browser authors seem to be among the kind of people who
don't read the README and fail to test with anything but their own
very limited set of hardware. =(

-ik

[Howlin' Alan]

A friend with an IDE64 did some testing for me, so I'm surprised you're having problems. The IDE64 should give you options to go to parent/root directories, just like the uIEC.  Have you actually tried it?

[Howlin' Alan]

On Wednesday, January 16, 2013 3:06:15 PM UTC-5, Ingo Korb wrote:

 

> When browsing a uIEC, there are parent and root options at the top of
> the disk directory.

I guess it's time to kill that silly distinction in the identification
message - file browser authors seem to be among the kind of people who
don't read the README and fail to test with anything but their own
very limited set of hardware. =(

 

I apologize if my poor contribution to our hobby, that costs you nothing, isn't living up to your expectations.

[Howlin' Alan]

I've made a silly mistake that probably makes Nav act crazed when reading some SD2IEC drives.

 

I've been reminded that I have a "very limited set of hardware", but that won't stop me from releasing a fixed version of Nav that people with "other" SD2IEC devices can use.

[Mike Paull]

That's a bit harsh don't you think.
Al has provided one of the best file browsers so far and at no cost to anyone.

If you're saying the parent/root options don't work on the IDE64 then have you got the CMD comparability turned on in the IDE64 config ???

The uIEC hardware uses the same command set so it's going to be most compatible with drives that conform to that spec. When I had my IDE64 I remember a BIOS option that allowed that comparability to be enabled/disabled.

Mike

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
> To post to this group, send email to uIEC-...@googlegroups.com.
> To unsubscribe from this group, send email to uIEC-users+...@googlegroups.com.

[Mike Paull]

Hi Al,

Like I replied to Ingo, I wonder if his problem can be fixed with the CMD option in the IDE64 bios.

Mike

Sent from my iPhone

On 17/01/2013, at 11:41 AM, Howlin' Alan <al...@bluesmanforhire.com> wrote:

I've made a silly mistake that probably makes Nav act crazed when reading some SD2IEC drives.

 

I've been reminded that I have a "very limited set of hardware", but that won't stop me from releasing a fixed version of Nav that people with "other" SD2IEC devices can use.

--

You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To post to this group, send email to uIEC-...@googlegroups.com.
To unsubscribe from this group, send email to uIEC-users+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/uIEC-users/-/r8sMZEJf0JgJ.

[Howlin' Alan]

On Wednesday, January 16, 2013 9:27:55 PM UTC-5, Mike Paull wrote:

Hi Al,

Like I replied to Ingo, I wonder if his problem can be fixed with the CMD option in the IDE64 bios.

 

 

Nav checks the boot up message from the drive and looks for "IDE64" in the string. I don't have an IDE64, but I did have a tester who does... was working fine for him.

 

re your post above... thanks

[Payton Byrd]

VICE has IDE64 support.  You should use it for testing. 

[Howlin' Alan]

On Wednesday, January 16, 2013 8:04:03 AM UTC-5, silv...@wfmh.org.pl wrote:

I see - so only for uIEC. I couldn't find a way to navigate up on IDE64. Not sure about 1581 now.

I've replaced the NAV downloads with a bug-fixed version that should now work properly with all SD2IEC devices. Helpful comments appreciated. 

[Ingo Korb]

Mike Paull <mike...@gmail.com> writes:

> That's a bit harsh don't you think.

No?

> Al has provided one of the best
> file browsers so far and at no cost to anyone.

That's nice, but it doesn't change the fact that some programmers use
detection routines that leave half of the user base out in the cold.

> If you're saying the parent/root options don't work on the IDE64 then
> have you got the CMD comparability turned on in the IDE64 config ???

I'm not sure what you're talking about here, I do not own an IDE64.

-ik

[Howlin' Alan]

On Thursday, January 17, 2013 3:08:54 PM UTC-5, Ingo Korb wrote:
> Mike Paull <mike...@gmail.com> writes:
> > That's a bit harsh don't you think.
>
>
>
> No?
>
>
>
> > Al has provided one of the best
> > > file browsers so far and at no cost to anyone.
>
> That's nice, but it doesn't change the fact that some programmers use
> detection routines that leave half of the user base out in the cold.
>

Thanks for the brilliant insight, you've really added a lot to the conversation. The Internet needs more people just like you.

[Ingo Korb]

Oh, don't worry. It's mostly an excuse to finally remove one of the two
different identification strings from the source and it's meant as a
general observation, not to specifically single you out. Your program
just happened to be the latest one with this problem and the first
one that looked nice enough for me to care.

At least you didn't try to use some pecularities in M-R for detection
like one of the cracking groups did. ;) (fails miserably if XR has been
used, e.g. for GEOS users)

-ik

[Snogpitch]

Since you are looking for helpful comments, I'll add my own here.

Since I didn't see any mention of a CMD RamLink in the tested
hardware, I thought I would test it out. Here's what I found, some
good and bad.

As NAV loads the directory for the current partition, all seems well.
I have a 1581 partition set as my default partition. I didn't see a
way to switch partitions, but, with the @ option, I was able to with a
command of CP3. The partition name and blocks free were displayed,
and the listing of files. One problem, however. When I navigate to a
directory that has no files, I get an ? syntax error in 1100. When
this happens, the program will not run again, I need to reset the
C64. Then load NAV again. Is there a sys command to launch it again,
perhaps after resetting the drives to their default state?

[Howlin' Alan]

On Saturday, January 19, 2013 7:19:31 AM UTC-5, David Witmer wrote:
> One problem, however. When I navigate to a
>
> directory that has no files, I get an ? syntax error in 1100. When
>
> this happens, the program will not run again, I need to reset the
>
> C64. Then load NAV again.

Thanks, I just noticed this too. Now that there are some people actually using NAV, I'm getting all sorts of bug reports, of course. I'll get out a new version in a month or two once I get it all cleaned up.

You know how to reach me, Dave. If you run across anything else, lemme know.

[Payton Byrd]

Al,

Yes, the Internet needs more people like Ingo.  If it wasn't for him we wouldn't have SD2IEC.  Be glad he's willing to participate and provide constructive criticism to the authors of the software that use his stuff.

[Luke Crook]

Is there a library of detection routines available, or must developers really start from scratch each time?

--

You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To post to this group, send email to uIEC-...@googlegroups.com.
To unsubscribe from this group, send email to uIEC-users+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/uIEC-users/-/QvXM_rQPFGYJ.

[Terry Raymond]

  Yeah I agree with Al and do appreciate Ingo's input, Al is right.  

> Yes, the Internet needs more people like Ingo.  If it wasn't for him we wouldn't have SD2IEC.  Be glad he's willing to participate and provide constructive criticism to the authors of the software that use his stuff.

Really, Payton? After three days or so, you decide to pile on? Afraid you were going to miss an opportunity to be a dick? Don't worry, you crept in right under the wire. Congrats.

[Payton Byrd]

WTF is going on around here?  I wasn't trying to pile on to anybody, and especially wasn't trying to be a dick.  I was trying to defend Ingo because of the awesome job he's done providing and supporting SD2IEC.  Lord knows I'm well aware of the pitfalls of releasing hobbyist projects to the wolves for critique and such.  You should read the comments on a lot of the stuff I've put out that's on CSDb.  I can choose to do one of two things: get butt-hurt and go away, or take the criticism and try to use it as incentive to get better at the stuff I make. 

[Payton Byrd]

On Tuesday, January 22, 2013 10:44:09 AM UTC-6, Luke Crook wrote:

Is there a library of detection routines available, or must developers really start from scratch each time?

I think people tend to start from scratch because they don't know what's out there for re-use.  Here's the code I use in EasyCLI to detect drive type.  I make no warranty to it's completeness, but the technique used isn't horrible.

http://easycli.codeplex.com/SourceControl/changeset/view/94877#2258515 

[silv...@wfmh.org.pl]

On 2013-01-25, at 03:35, Payton Byrd wrote:

>
>
> On Tuesday, January 22, 2013 10:44:09 AM UTC-6, Luke Crook wrote:
> Is there a library of detection routines available, or must developers really start from scratch each time?
>
> I think people tend to start from scratch because they don't know what's out there for re-use.

Well.. there isn't a lot of a need to re-use "Hello, world" type of prg, is there? ;-)

> Here's the code I use in EasyCLI to detect drive type. I make no warranty to it's completeness, but the technique used isn't horrible.
>
> http://easycli.codeplex.com/SourceControl/changeset/view/94877#2258515

Parsing the DOS mismatch string is the normal way, gron-ups use ;-) Reading ROM for some sequences reminds me of my good old friend who preferred to read from KERNAL ROM rather than write LDA #'$' to get the character required for reading directory..

Someone who writes for uIEC should know by now that uIEC runs on SD2IEC based firmware for some time now already and that detecting "uIEC" means more or less detecting "SD2IEC compatible device".

--
SD!