I did some testing and found that *\whatever.exe does not work, while *whatever.exe does. In case anyone thinks to themselves, "but that could cause problems for xwhatever.exe!", I tested further and found that it only affects programs with the name whatever.exe and not those such as xwhatever.exe.
-- Jeff S.
We could add this to show different behaviours :
; you can specify applications too ; This one will apply for all notepad.exe ;"*\notepad.exe" = "native, builtin" ; This one will apply only for a particular file ;"C:\regedit.exe" = "native, builtin"
Is everyone ok ?
_________________________________________________________________ Get faster connections -- switch to MSN Internet Access! http://resourcecenter.msn.com/access/plans/default.asp
On Wednesday 23 October 2002 09:05 am, Jeff Smith wrote:
I did some testing and found that *\whatever.exe does not work, while *whatever.exe does. In case anyone thinks to themselves, "but that could cause problems for xwhatever.exe!", I tested further and found that it only affects programs with the name whatever.exe and not those such as xwhatever.exe.
This is really confusing IMO. When people see *[filename] they're going to think of shell globbing, whether we want them to or not. Perhaps "*\whatever" /should/ be the supported syntax?
--- Greg Turner gmturner007@ameritech.net wrote:
On Wednesday 23 October 2002 09:05 am, Jeff Smith wrote:
I did some testing and found that *\whatever.exe does not work, while *whatever.exe does. In case anyone thinks to themselves, "but that could cause problems for xwhatever.exe!", I tested further and found that it only affects programs with the name whatever.exe and not those such as xwhatever.exe.
This is really confusing IMO. When people see *[filename] they're going to think of shell globbing, whether we
want them to or not. Perhaps "*\whatever" /should/ be the supported syntax?
I agree
__________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/