Well if you used call and redirected input couldn't you just get environment variables? There was also a registry dialect I saw once, if you used that I suppose you would be able to check the registry structure, not particularly stable a method either, but I think it's better than checking if c:\windows exists; I've worked with people who, in building programs would check if c:\winnt existed and if not create it so they could have a c:\winnt\system32 to put their dlls in and it took repeated explanations as to how to handle the problem correctly over a space of 6 months to get them to actually change their original code so as a consequence I don't believe in every checking against the existence of a folder and assuming from that what operating system one is in.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ashley Tr�ter Sent: Friday, October 31, 2003 2:24 AM To: [EMAIL PROTECTED] Subject: [REBOL] Re: creating a shortcut Good news indeed! So now I can create a Windows shortcut with the following: create-link/start "c:\MyApp\MyApp.exe" "c:\Documents and Settings\All Users\Desktop\MyApp.lnk" "c:\MyApp" on Windows2000/XP. I suppose on 95/98/ME I can check for the presence of "c:\Windows" and replace "c:\Documents and Settings\All Users\Desktop\MyApp.lnk" with "c:\Windows\Desktop\MyApp.lnk". Anyone come up with a better (more generic) approach to handle this? Regards, Ashley -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject. -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
