Jump to content
SAU Community

Howto: Automatic Windows Background Changer

paulr33

By paulr33,
in Tutorials / DIY / FAQ

 Share

Recommended Posts

paulr33 Grand Master

paulr33

Posted
Posted

HOWTO: Automatic Windows Background Changer

Intended Audience: Anyone who uses Windows and would like an automatic background changer

Technical Level: Easy

Duration: 30 minutes

Effort: Easy

Result: Excellent

OS Supported: Windows 9x/NT/2000/XP/2003

Requirements: Windows .NET Framework (Ver 1.0 or higher) - From Windows Update or Direct Link

Dual Head Supported: Yes

!!!Caution/Achtung/Attenzione!!!

Follow this guide at your own risk. You have been warned. We are not responsible for any actions you take. The information contained herein is a guide and should be acted upon with consultation from your local tuner. If you are unsure or are not confident don't do it.

The programmers at my work have written a quick little Windows desktop changer that cycles through a folder with pictures in it and selects an image at random at each interval (settable) and set it as your Windows desktop background. You can manually force an update of your desktop or wait for the specified interval in seconds. Follow the below steps to install it:

1). Make a folder with some pictures in it. At least 1 picture. "My Pictures" is perfect for this if you wish

2). Make sure you have Windows .NET runtime installed (from Windows Update or the URL at the top).

3). Download wchanger.exe

4). Create a shortcut in your Startup folder to wchanger.exe or you can even copy the .exe to the Startup folder if you wish.

5). Run wchanger.exe and it should place an icon in your system tray which will be an orange wavey icon. Right click and "Select picture directory" and choose your folder. You can also set the interval and try a manual "Force update" to make sure it's working.

Thats it.

I have my wchanger.exe pointing to an SAU folder which has over 1400 images from various SAU events, people, cars, parts, engines etc so there's always something interesting on the desktop. I use this app at work also with the same folder to keep me entertained.

  • 1 month later...
  • 3 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


  • Similar Content

  • Latest Posts

    • Kapr
      RB20DE NEO smallbox clutch.

      By Kapr · Posted

      For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • GTSBoy
      Mistakes were made, my R34 Story

      By GTSBoy · Posted

      Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • Kinkstaah
      Mistakes were made, my R34 Story

      By Kinkstaah · Posted

      I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • GTSBoy
      Mistakes were made, my R34 Story

      By GTSBoy · Posted

      No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • Kinkstaah
      Mistakes were made, my R34 Story

      By Kinkstaah · Posted

      God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...