10.4 and 10.5 are very different.
Besides it doesn't need to be a virus to do damage. You could have damaged something unintentionally even.
Just FKIN TRY IT and stop doubting me fk sake you either wanna see what cool stuff it does or you dont and btw i have read all the change logs between 10.4 and 10.5 and not much really has changed other than minor changes ........ im not dumb
And there is nothing potentially harming as i wrote it in fking terminal and im a noob at doing this so i dont know nothing off of the basics so dont talk b'lox this works on both my macs.............
oh and btw i wrote scripts for powermad and he dont seem to have any problem and i also sent my script to pyrite for reviewing and hes on 10.2
If your gna try it, try it .......... good
If your not then please stop wasting my time ......... KTHXBAI!
CandyMan is right, it doesn't need to be a virus to do damage.
Nothing potentially harming "because you wrote it in a terminal and you're a noob at doing it"? That's the kind of thing CandyMan is describing - if you don't know what you're doing you could unintentionally damage vital files.
Also, curb your language please, there's no need to swear at people and generally be offensive over it, especially as all CandyMan is doing is being cautious over code that he has no idea what it does, which he is justified in being so.
You can actually run stuff from a terminal and close the terminal without the process ending by appending "&" after the command, then issuing "disown". "&" backgrounds the task allowing you to retain use of the terminal, and "disown" does exactly what it sounds like. So you can run (for example) "firefox &" then "disown" then close the terminal, and firefox will persist. I'd assume this works for Mac too.
EDIT: Found this on a Google search:
display dialog "Select the desktop background type:" buttons {"Cancel", "Normal", "ScreenSaver"}
if button returned of result = "ScreenSaver" then
do shell script "/System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background > /dev/null 2>&1 &"
else
tell application "System Events"
if process "ScreenSaverEngine" exists then tell application "ScreenSaverEngine" to quit
end tell
end if
It's an AppleScript that does the same thing. The command that actually sets the background as the current screensaver is
/System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background
The rest is just a nice wrapper for it.