Showing posts with label tool. Show all posts
Showing posts with label tool. Show all posts

Wednesday, June 26, 2013

Tool to Keep Hard Drives Awake

Requirements

This application uses .Net 3.5.  .Net 3.5 is included in Windows 7.  Windows Vista and XP users will need to make sure .Net 3.5 is installed to use this application.  An easy way to tell is if you open this program and it immediately errors, you probably don't have it :)

Description

I wrote this tool because the tools I found on the net did not exactly meet my needs.  xSleep works well, but it is stubborn config wise.  I changed it to monitor a different second drive, and whenever I reopen it, it goes back to the previous setting.  The other tool I found only let you add one drive.

This tool let's you add as many drives as you want.  You can have it open to the systray.

The last three external USB hard drives I have purchased all seem to have a power saving mode implemented through firmware.  Power settings changes in Windows 7 did not resolve the issue.  I need to keep these drives from going into power saving mode as it interferes with my Media Center processes.

Installation


Download






Extract the KeepAwake.exe to any location your prefer.

Usage

Open KeepAwake.exe.  Add the drives you want to prevent from going into a power saving mode.  When ready, click the Start button.  Once Start is clicked the application is active and will 'ping' the specified drives at the set interval. 

This application works by writing a text file to the root of the specified drive at the set interval.  After the file is written it is deleted.  The contents of the file is a list of the directories on the drive.

Options  - all options are remembered by the application.
  1. Keep awake interval (how often the drive is 'pinged') - set number in minutes
  2. Start on Open - tells the application to go ahead and start monitoring as soon as it is opened (recommended).
  3. Open to Systray - when the application opens there will not be a visible window.  Just a lightbulb icon in the systray area (down by the clock in the lower right).
  4. Automatically run at logon - checking this box will cause the program to automatically run when the current user logs onto the system.
The intentions of options 2,3, and 4 are so once the app is configured it will automatically run when the system is logged on and will be hidden in the systray.  Verification that the app is actually doing something can be seen in the list box on the right.  The wrote file and deleted file, with timestamps are listed.

Note, deselecting the box for Automatically run at logon will delete the startup shortcut.  If you plan to move the location of the .exe, or remove the .exe all together, and have enabled auto run, please uncheck this box first so you do not have messages at logon about a missing file (the shortcut will still be in startup pointing to something that no longer exists).  If you move the .exe, just uncheck, move, and then re-check the box and a new shortcut will be created pointing to the new location.

Right clicking the systray icon allows to choose 'Exit'. Clicking the systray icon opens the KeepAwake window.  Minimizing KeepAwake moves it to systray.  X'ing out closes the application.

Screenshot

 

Troubleshooting

If you have any issues with the program please post them in the comments section.


Tuesday, June 09, 2009

Transcode 360 Installer Tool

New get you up and running quickly Transcode 360 installer tool download

New Version Available
There was an issue with the previous version. In the ServerAddress Reg Edit portion, it was filling in the box with IPv6 addresses in some cases. IPv6 addresses will produce an error like "A port was expected because of there is a colon present but the port could not be parsed". I wrote instructions below how to fix this, or you can uninstall the existing copy of the tool, download and install the new one, and just run the ServerAddress Reg Edit part again.

There was also an issue with one of the builds where it was not replacing the ffmpeg.exe properly. That has been fixed.

I also took out the .Net 1.1 checker and the files from the download. The tool is much smaller download now.

The latest build of the tool is 1.05

Introduction
There is more to getting Transcode 360 installed and working than just running that actual installer. This blog post outlines many of the steps required to get T360 up and running.

It's a bit tedious. Also, it's the number one reason people come to my blog - instructions on how to install T360.

I've made an installer tool that will take care of getting T360 setup for you. Basically, you should be able to run this tool and accomplish the same thing you would by reading the instructions and performing the different steps as you go.

You need .Net 2 Framework install to use this tool. If you don't have it you can get it here. I'm not sure, you may need to run Windows Update after the install and apply the .Net 2 service pack also.

The link to download the tool installer is at the top of this post.

When you open the tool, there is a link to instructions on the right. Have a look. The PDF version is much nicer on the eyes.

This tool is designed to get you up and running is you 1) are using Media Center 32-bit, 2) Have your movies stored on your Media Center. If you are using 64-bit, Transcode 360 probably will not work. If you are storing your movies on a NAS or another computer, you can still use this tool to get things setup, but you will need to go back and make some more adjustments for your enviroment. I have blog posts with instructions (and another tool).

Troubleshooting

When you try to watch a movie from your extender, and you get the error:
"A port was expected because of there is a colon present but the port could not be parsed."
It is probably that on the ServerAddress part, it used your systems IPv6 address, rather than the required IPv4 address. IPv6 addresses look like this xxxx:xxxx:xxxx:xxxx. To fix this you need to run the tool again, but only the ServerAddress Reg Edit part. In the box put your Media Center's IPv4 address in the box and click Run button. Reboot the Media Center and try your extender again. If you do not know you Media Center's IPv4 address do this:



  1. Go to Start>All Programs>Accessories>Command Prompt
  2. At the prompt type: ipconfig and then hit Enter key
  3. You should get some lines of information back. One will say IPv4 Address. Write down the address.
  4. Go back and run the installer tool. Type the address you wrote down into the box, and click the Run button to the right.
  5. Reboot the Media Center and try your extender again.
One of the builds of the tool did not replace the ffmpeg.exe correctly. If you download the posted version, you can click the button in the mencoder/ffmpeg part and it will fix the missing ffmpeg.exe file.

New beginner's guide to PowerShell on my GitHub page

 I created a beginner's guide to PowerShell here: https://github.com/aamjohns/Powershell_Guide/blob/main/README.md I hope it helps someo...