----- Original Message ----- From: "Sylvain Petreolle" spetreolle@yahoo.fr To: "Tony Lambregts" tony_lambregts@telusplanet.net; "Dustin Navea" speeddymon@sbcglobal.net Cc: "Sylvain Petreolle" spetreolle@yahoo.fr; "Wine Developers" wine-devel@winehq.com Sent: Sunday, December 08, 2002 5:11 AM Subject: Re: Loading Autorun.inf on CD's
If you want act in this way, I have something for you. This could help Paul Jones, who is searching how to "launch" *.msi installers.
interesting
The better way we can handle this is a program who tries to open every document we give to it. A freeware utility exists in cygwin world and is called cygstart, using the existing registry. If we give it a .doc, it looks in HKCR and starts Worpad/Winword.
That is a definite must..
If we tweak the registry of a .inf (winedefault.reg), we can ask it to launch a tiny program that will open the .inf and run the program specified.
Sounds like it could work, but what about inf installer files (ie TweakUI's inf, or driver inf files) how would they be handled?
I have not seen this work either and definitely not with an .inf. Yes it would be cool and if you want to start a bug concerning it feel free. I am not that worried about it though. The way I see it is that most of
this is not realy a wine problem but rather with setting up autorun so that it is able to understand what to do with an .inf file. I suppose
another way to look at it might be that wcmd could/should be able to handle something like "wcmd autorun.inf".
-Dustin
If we tweak the registry of a .inf (winedefault.reg), we can ask it to launch a tiny program that will open the .inf and run the program specified.
Sounds like it could work, but what about inf installer files (ie TweakUI's inf, or driver inf files) how would they be handled?
Generally, .inf files are all installer files, only the autorun.inf is something special. If the file on the CD is named differently it doesn't work anymore. So we would just have to check for this name. I don't know how it is done on Windows, what makes the auto-insert check. But whatever program gets the insert notification it should call 'wine wineautorun.exe autorun.inf'. Wineautorun.exe will parse the autorun.inf. And all other .inf go to the installer.
bye Fabi
That is basically what I have been saying.. sorry for the html output but I am replying from work thru sbc's site and theres no option to turn it off. Basically, we need wineautorun.inf to parse the file autorun.inf or Autorun.inf on CD's If you try to run a non-autorun file it pops up a dialog saying hey this isnt an autorun inf and so I cant do anything with it! The parsing itself shouldnt be too hard, but AFAICT the windows autorun loader only looks for autorun.inf (Case Insensitive) and parses it for the icon and the file to actually run. If we implemented this, it would make things a lot easier for v1.0 because users wouldnt have to learn command line just yet.. Fabian Cenedese Cenedese@indel.ch wrote:
If we tweak the registry of a .inf (winedefault.reg), we can ask it to launch a tiny program that will open the .inf and run the program specified.
Sounds like it could work, but what about inf installer files (ie TweakUI's inf, or driver inf files) how would they be handled?
Generally, .inf files are all installer files, only the autorun.inf is something special. If the file on the CD is named differently it doesn't work anymore. So we would just have to check for this name. I don't know how it is done on Windows, what makes the auto-insert check. But whatever program gets the insert notification it should call 'wine wineautorun.exe autorun.inf'. Wineautorun.exe will parse the autorun.inf. And all other .inf go to the installer.
bye Fabi
-
Dustin Navea -
Fabian Cenedese