autorun.lha utility/misc - Comments

HKvalhe (80.213.142.202) @ 11 Apr 2014, 02:34.18

Fri, 11 Apr 2014 14:34:18 +0200

By: HKvalhe (80.213.142.202)

Thank you for bringing this tool. It's very useful! :)

Elwood (77.203.117.25) @ 14 May 2011, 03:15.26

Sat, 14 May 2011 15:15:26 +0200

By: Elwood (77.203.117.25)

nice idea Fredrik. Good job!

Rigo (94.170.78.48) @ 13 May 2011, 01:27.37

Fri, 13 May 2011 13:27:37 +0200

By: Rigo (94.170.78.48)

Very nice. This is a almost identical to the AutoRun program I did for the AmigActive CDs where the CD could be set up when the user puts it in the drive. 
 
It's nice to see this functionality come to OS4.

kas1e (78.36.139.250) @ 26 Sep 2010, 09:31.40

Sun, 26 Sep 2010 09:31:40 +0200

By: kas1e (78.36.139.250)

52.2 version rokz because of that sys:s/autorun-default feature. Already tested, and it works fine (for testing i just do "newcli"), and when i put for example by usb stick, or mount archive by xadmount, it spawn for me newcli.

PEB (75.34.41.217) @ 24 Sep 2010, 09:23.43

Fri, 24 Sep 2010 21:23:43 +0200

By: PEB (75.34.41.217)

What would be kind of nice is if some default action could be set for an inserted volume that does NOT have S/AutoRun script present (such as automatically opening the root of the volume in a WB window).

anonymous (46.114.139.175) @ 24 Sep 2010, 04:06.20

Fri, 24 Sep 2010 16:06:20 +0200

By: anonymous (46.114.139.175)

@TSK: 
 
This doesnt make much sense... imagine inserting a CDRW containing some backup of your very old OS3.x system into the drive of your modern OS4 system. Executing the OS3 startup-sequence wouldnt help much ;) 
 
Besides that, why should any other script be "incompatible"? 
startup-sequence is meant to be executed on _startup_ of the system (and from the boot device), not on any point after startup (which is what autorun is meant for) and from a non-boot device.

TSK (84.248.40.19) @ 24 Sep 2010, 03:16.50

Fri, 24 Sep 2010 15:16:50 +0200

By: TSK (84.248.40.19)

Could you make it run S/Startup-sequence instead to make it backwards compatible/traditional ?

whose (46.114.139.175) @ 24 Sep 2010, 12:37.23

Fri, 24 Sep 2010 12:37:23 +0200

By: whose (46.114.139.175)

Yeah, security issues should be of concern. 
 
Nonetheless, together with all your nice filesystems and handlers, its a great thing. Best bit is installing from inside an archive, done via XAD filesystem. One bit more "autorunned" than all other systems do. As soon as XAD filesystem is part of a standard installation, users are able to install programs without dearchiving to RAM:, one step less for the lazy people ;)

orgin @ 24 Sep 2010, 10:30.50

Fri, 24 Sep 2010 10:30:50 +0200

By: orgin

If not already in there then add a way to get a requester asking "this device has a autorun script, do you want to run it?" before the script is executed for security reasons. 
 
Also a way to block certain devices.

kas1e (95.54.77.218) @ 24 Sep 2010, 09:33.54

Fri, 24 Sep 2010 09:33:54 +0200

By: kas1e (95.54.77.218)

Pretty interesting. Maybe it even can be as one more commoditie for OS by default.

salass00 (94.101.5.193) @ 24 Sep 2010, 06:32.50

Fri, 24 Sep 2010 06:32:50 +0200

By: salass00 (94.101.5.193)

The script file is inside the inserted volume. 
 
F.e. if I added the following commands to a file called S/AutoRun inside diskimage.device release archive: 
CD diskimage_device 
Installer Install APPNAME diskimage.device MINUSER EXPERT DEFUSER EXPERT 
 
Then when I mount the archive with MountXAD f.e. by double-clicking on it if I have MountXAD configured as default tool it will start the installer script automatically.

PEB (99.141.30.161) @ 24 Sep 2010, 12:11.22

Fri, 24 Sep 2010 00:11:22 +0200

By: PEB (99.141.30.161)

Nice idea! 
 
Can you provide an example script that shows how to have different actions taken for different volumes? 
 
Thanks.