|
Post by Chris Iverson on Nov 14, 2018 16:54:36 GMT
Just upload it to any filesharing site so we can download it. I can even provide you with an account on one, if you don't want to bother signing up somewhere.
|
|
|
Post by Rod on Nov 14, 2018 17:38:11 GMT
Ah, progress. So a correct path to the token file as the first parameter works. Good learning and info for folks.
|
|
rickh
Member in Training
Posts: 27
|
Post by rickh on Nov 15, 2018 17:16:43 GMT
Well it gets worse (at least from my perspective). If I put in the command listed back (as shown with the 'expected information') and make the first parameter as the path to the TKN file (which is where I ran the EXE file from) it works. It works even if I add the other 8 simple string parameters. BUT if I replace ANY of those other 8 strings with a duplication of the path to the EXE/TKN file (or any path) it errors out with the 'Application Load Aborted' box containing File Not Found: CLtest.TKN OK.
\s\Rick
|
|
rickh
Member in Training
Posts: 27
|
Post by rickh on Nov 16, 2018 19:05:45 GMT
|
|
|
Post by Chris Iverson on Nov 16, 2018 21:47:15 GMT
Ok, I definitely see the issue here, and it's not just an issue in JB, either, but it's an issue that was probably introduced in LB v4.5.1, which JB2 is based on. It doesn't occur in LB v4.04, which is what JB1 was based on. Your explanation in the README you provided appears to be correct: if a backslash appears anywhere in one of the parameters passed, LB/JB will automatically assume that it's supposed to be the path to the TKN, and will then error out. EDIT: More accurately, it will automatically assume that everything before the final backslash in the whole CommandLine$ string is part of the "Default Directory", where the TKN should be found. If you manually count that out, and make a folder with that "name", and stick the TKN there, it will launch. I just made a test application that demonstrates a ton of issues, that I'm going to report on the main LB page, as well as here. EDIT2: Oh, even better. Quoting the TKN path lets it launch properly, but then it completely ignores the rest of the CommandLine$, and doesn't pass it to the program. EDIT3: Made a post on the LB forums about this bug, as well as detailing a bunch of examples. libertybasiccom.proboards.com/thread/352/command-line-path-parsing-bugs
|
|
|
Post by tsh73 on Nov 17, 2018 9:36:39 GMT
Wow. Thanks for digging this out. Hope Carl could sort this.
|
|
rickh
Member in Training
Posts: 27
|
Post by rickh on Nov 17, 2018 16:50:16 GMT
Good show Chris. Now that you have an even simpler bit of code I will take down the dropbox posting.
I can say if the sum total of all the parameters, from the last back to the first, concatenated together, is the proper path to the TKN file this will still work. So in my code (.\ being shortcut to my CWD, Current Working Directory):
this works as you stated
.\cltest .\ P3
as does this .\cltest .\ P3 P4 P5 P6 P7 P8 P9 P10
this doesn't as you stated: .\cltest .\ p3 .\
this does: .\cltest .\ .\ .\ .\ .\ .\ .\ .\ P10
so does this: .\cltest .\ .\ .\ .\ .\ .\ "" "" P10
So I now ask what was the driving force behind changing V1 behavior and put a path to a token file into the command line parsing?
I perceive command line as user space. I have made my pitch before for maintaining that space as user space and that alternate path to a token file be in command space but I do not know what request or need might have been satisfied by putting that path into the command line space.
Since I can continue to use the V1 environment I have no critical needs to go to V2. By installing V1 in a path that is not Program Files or Program Files (x86) several years ago, I chose C:\oldtools, I can continue to develop programs under V1 for the foreseeable future under Windoze V7.
Thanks to all \s\Rick
|
|
rickh
Member in Training
Posts: 27
|
Post by rickh on May 8, 2019 21:07:14 GMT
So I am wondering if there is life for me and V2.x of Just Basic?
Chris posted here, 16-Nov-2018, and in the Liberty Basic forum, also 16-Nov-2018, (which I don't follow) about the change in how the two recent issues of the programs (LB4.1.x and JB2.0) deal with parameters passed into them differently than the previous versions. Since I am not a member in LB I will post my query here. (if someone wants to repost this in LB I have no problem with that).
I still believe that adjusting paths to token files should be done in a command line using switches to modify the execution and that the parameters that CommandLine$ picks up should be pure user space as was in V1.0. If in my use of CommandLine$ in V2.x I want to provide my program with any path to my data files then I must first insert a, unnecessary for me, path to a token file which is already in the same directory as the executable as was found in the V1.0 documentation I read.
Since I don't think I have seen anything here (or LB forum) from a Developers I don't have a feeling for how this could go. Not sure if it will get addressed or declared a new feature, then documented and left in as is?
thanks for listening \s\Rick
|
|
rickh
Member in Training
Posts: 27
|
Post by rickh on Feb 19, 2020 21:41:31 GMT
Will V1.01 run on Windoze 10?
\s\Rick
|
|
ntech
Junior Member
Posts: 99
|
Post by ntech on Feb 20, 2020 2:25:59 GMT
rickh, I've been able to run v1.01 on Windows 10 without any significant issues.
|
|
|
Post by Rod on Feb 20, 2020 8:41:15 GMT
Yes we were all mostly running v1 on Win 10 before v2 came along. Must the file list be passed in the command line? Could you not write the list to a file and just BASIC pick that up.
|
|
rickh
Member in Training
Posts: 27
|
Post by rickh on Mar 25, 2020 14:39:52 GMT
Thank you both for replying. I guess I will be able to move forward at least for now.
Have to say that I got a Forum update notification that ntech had replied but not with Rod's reply so I am late getting back here with a 'thank you'.
No Rod I cannot change this program, perhaps with a re-write the others maybe. This program is delivered on a CD/DVD with a token and the standalone RT environment. A user (of any level) may run it as-is, without any install/move/copy etc, from that environment. Just Basic was the only compiler that I found which had this feature of a standalone mode.
\s\Rick
|
|