Re: using STRPCO, STRPCCMD to launch a browser app.

https://archive.midrange.com/midrange-l/200908/msg01197.html

Scott says,
"I've tried doing it the way Booth shows (with the "start" command), and
I've also tried doing it the way Brian May/Nick Radich shows (with
FileProtocolHandler).

I'll tell you this: Brian/Nick's solution (FilePrototcolHandler) is MUCH
MUCH nicer. It doesn't create the ugly MS-DOS window, it has much fewer
problems with special characters in filenames and URIs. It's just a much
better solution.

My 2 cents.
​"

Charles​

On Tue, Oct 10, 2017 at 10:52 AM, Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx> wrote:

for many years, we have some CL programs that will run the STRPCO and
STRPCCMD's to start a browser app.

we had prefixed our url's with the windows commands:
rundll32 url.dll,FileProtocolHandler

(rundll32 url.dll,FileProtocolHandler
https://xyz.domainname.com/appname/landingpage)


I now see some examples using the windows start command:

START " " "https://xyz.domainname.com/appname/landingpage";

this appears to work fine, but can anybody who does this comment on any
problems or benefits of using START vs. rundll32 url.dll ?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD