× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott,

Why is the shell32,ShellExec_RunDLL better than url.dll,FileProtocolHandler,
exactly?

Rory

On Fri, Apr 2, 2010 at 1:58 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>wrote:

hello,

The FileProtocolHandler thing still works... but here's a slightly newer
way to do it:

CHGVAR VAR(&CMD) VALUE('rundll32.exe +
shell32,ShellExec_RunDLL ' *BCAT +
'http://www.' *CAT &SITE *TCAT '.com')

Either way is 1000 times better than the hard-coded path that DLee
posted. Hard-coding the location of a file is a bad idea. What if MS
decides to store IE in a different location? What if different PCs have
it in different locations? Not to mention that the user might want to
use a different browser. Or that the hard-coded path name is longer and
therefore gives you less space for the URI...


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.