Re: SixPack mods for Linux users

Paul, et alia:

It may work with Vista, but so what? Many of us are trying to run a 1970s mainframe OS, why is it so far fetched that people would be running Windows 2000 that might not support this?

At any rate, I was just suggesting it was another way to be able to support both Windows and Linux using a more standardized config file.

I am by no means insulted if you do not wish to use the config file I submitted, thats entirely fine by me. I am using mine (obviously) and so if you can use it and it helps you, great, if not, great too!

I am going to try to look at all the batch files in the SixPack and see if I can Linux-ize them too.


Blake


--- In [email protected], "kerravon86" <kerravon86@...> wrote:
>
> --- In [email protected], Dave McGuire <Mcguire@> wrote:
> >
> > On 10/17/10 2:34 AM, "Fish" (David B. Trout) wrote:
> > > [...]
> > >> It's not Windows that deals with "/", but it's Hercules (a program)
> > >> that reads the config file and accepts both "\"  and "/".
> > >>
> > >> Windows by itself doesn't support "/".
> > >
> > > Incorrect.
> > >
> > > Windows has supported *either* forward slash *OR* 
> > > backward slash for many, many years now.
> > 
> >    Every time I accidentally type '/' (the two or 
> > three times a year 
> > that I have to do something on a Windows box ;)) it 
> > doesn't work, at 
> > least in a "cd" command at a prompt.
> 
> It works for me with Windows Vista ...
> 
> C:\devel>cd pdos/s370
> 
> C:\devel\pdos\s370>cd ../..
> 
> C:\devel>
> 
> But I was surprised to see that.
> 
> > Do you mean in fopen() calls (or 
> > whatever the Windows API equivalent is)?
> 
> It was only this that I expected to work, as the
> system call has accepted a "/" from way back in
> the MSDOS days, as far as I can remember.
> 
> So because the API works, it is then up to the
> individual application if it does any edit
> check on that.
> 
> BFN.  Paul.
>