Posts Tagged ‘Solutions’

Since my warranty was already void as of 12/07, and because I already swapped the 30GB HDD for a 60GB HDD, I ended up opening the Zune, then reseating the cable from the battery to the main board which resets the Zune (it’s the little brown plastic piece on the right in the attached photo, the one with the long cable going to it over the hard drive).

It seems as long as the Zune isn’t sync’d again with the software open it should function. I’m still in the process of testing this but I’m guessing jumping the clock forward to Jan 1, 2009 may let things pass over fine. But then again I don’t really suggest doing this after you get it working .

Of course, I don’t suggest voiding the warranty by opening up your Zune either. Hopefully you won’t.

UPDATE: Now that we’re in good old 2009 the Zune has righted itself thanks to the infinite loop ending. All is right in the world and the final FAQ regarding the Zune resurrection has been posted on the proper Zune support site.

UPDATE: Gizmodo posting first on the reseat fix though I don’t believe you need to unplug the hard drive so I advise against that. I also suggest waiting for the official solution to come from Zune support.

UPDATE: From the Zune forums:

Early this morning we were alerted by our customers that there was a widespread issue affecting our 2006 model Zune 30GB devices (a large number of which are still actively being used).  The technical team jumped on the problem immediately and isolated the issue: a bug in the internal clock driver related to the way the device handles a leap year.  The issue should be resolved over the next 24 hours as the time change moves to January 1, 2009.   We expect the internal clock on the Zune 30GB devices will automatically reset tomorrow (noon, GMT). By tomorrow you should allow the battery to fully run out of power before the unit can restart successfully then simply ensure that your device is recharged, then turn it back on.  If you’re a Zune Pass subscriber, you may need to sync your device with your PC to refresh the rights to the subscription content you have downloaded to your device.

Customers can continue to stay informed via the support page on zune.net (zune.net/support).

We know this has been a big inconvenience to our customers and we are sorry for that, and want to thank them for their patience.

Q:  Why is this issue isolated to the Zune 30 device?

It is a bug in a driver for a part that is only used in the Zune 30 device.

Q:  What fixes or patches are you putting in place to resolve this situation?

This situation should remedy itself over the next 24 hours as the time flips to January 1st.

Q:  What’s the timeline on a fix?

The issue Zune 30GB customers are experiencing today will self resolve as time changes to January 1.

Q:  Why did this occur at precisely 12:01 a.m. on December 31, 2008?

There is a bug in the internal clock driver causing the 30GB device to improperly handle the last day of a leap year.

Q:  What is Zune doing to fix this issue?

The issue should resolve itself.

Q:  Are you sure that this won’t happen to all 80, 120 or other flash devices?

This issue is related to a part that is only used in Zune 30 devices.

Q:  How many 30GB Zune devices are affected? How many Zune 30GB devices were sold?

All 30GB devices are potentially affected.

UPDATE: Over at ZuneBoards.com, a moderator has posted up the source and analysis for the cause of the bug on the Zune 30’s. Pretty interesting. In the end a minor mistake and a missed test case causing a major headache. Likely a simple firmware update will prevent the problem again next leap year. Granted I doubt any Zune 30’s will even be able to hold a charge by then:

year = ORIGINYEAR; /* = 1980 */

while (days > 365)
{
    if (IsLeapYear(year))
    {
        if (days > 366)
        {
            days -= 366;
            year += 1;
        }
    }
    else
    {
        days -= 365;
        year += 1;
    }
}

I was using something else before, Feedburner I guess, I suppose I could keep using it, but it seemed limited. While using Redfin today I noticed they had the Share on Facebook with the down arrow and that it was using the AddThis.com service. Registered real quick grabbed the generated code and popped it in. Had to refer to the macro definitions for dasBlog but it seems to be working right now, the code looks like this:

<!– ADDTHIS BUTTON BEGIN –>
<script type=”text/javascript”>
addthis_pub = ‘YOUR USER NAME’;
</script><a href=”http://www.addthis.com/bookmark.php” onMouseOver=”return addthis_open(this, ”, ‘<%PermalinkUrlRaw%>‘, ‘<%itemTitleRaw%>‘)” onMouseOut=”addthis_close()” onClick=”return addthis_sendto()”><img src=”http://s9.addthis.com/button1-addthis.gif” width=”125″ height=”16″ border=”0″ alt=”" /></a><script type=”text/javascript” src=”http://s7.addthis.com/js/152/addthis_widget.js”></script>           
<!– ADDTHIS BUTTON BEGIN –>

This will work well for any dasBlog user just change the username, users of other services will need to figure out the permalink url and item title macro for their service.

This is a fairly common problem which leaves a lot of users scratching their heads as to how to just make things work. There are a couple reasons one would encounter this. The most common is because an application or process still has the file open (technically it’s called a ‘handle to the file’). Another possibility would be if the permissions on the file you were trying to delete were invalid. Without getting too in depth into the how and why there are two quick things to check on when trying to get around the problem.

I’ll go over the first reason in this post. In the Windows SysInternals suite, there is a tool called Process Explorer, which is an amazingly powerful app. It will allow you to view what’s going on behind the scenes of most everything running on the system. Just doing quick search will show just how powerful this tool is. For this issue though, what we’ll do is find any open handles on the file we’re trying to access and delete.

1. First, start Process Explorer.
2. Press CTRL+F to open a search window.
3. In the ‘Handle or DLL substring’ field type in a portion or the complete name of the file you are trying to delete and press Enter to begin the search. In my case the file was ”08 mer du japon.mp3″.
4. You should now be presented with a list of open handles. Next double click on the handle in the search window to show the file handle highlighted in the lower pane along with all the other open handles on the system.
5. Right click the row for the handle and click Close Handle.
6. You should now be good to go.

In this particular case it would seem the handle to the .MP3 file wasn’t properly closed by Windows Media Player despite it having finished playing and updating the metadata. Because of this I was unable to move the album folder. By using Process Explorer I was able to find the culprit and close down the handle which allowed Vista full access to move the file and folder. There are some other third-party tools available as well as other tips and ways of doing the same thing. However, I highly recommend the method I just described, as using and further exploring Process Explorer and the other tools available in the SysInternals suite of applications will allow you to gain a much greater understanding of your system.

This, combined with a few good search queries, a deep curiosity through Wikipedia, and the Microsoft Knowledge Base will help turn any enthusiast into a real power user. Check back shortly for part two where I discuss how to take back ownership of your files and folders through permissions in Windows Vista and Server 2008.

I was in a team meeting thing the other day and had my laptop out taking notes. Unfortuantely despite the fact I always run with all system sounds off, I kept on getting the annoying system beep every so often. It was maybe coming from Outlook and holding down the backspace for too long. It happens even if you mute the sound on the system, and heck, even if you disable the “System speaker” device in Device Manager which is listed under the System devices. And man is the beep loud, amusing really, since the mono speaker on my Dell Latitude D430 is barely audible but that bloody system beep is loud as hell and definitely attention grabbing.

So here’s how to disable the Beep, yes that’s actually what it’s called.

1. Press WIN+R
2. Type in devmgmt.msc and press Enter.
3. Click the View menu then click Show hidden devices.
4. Expand the Non-Plug and Play Drivers branch out.
5. Look for Beep and double-click the device to bring up the properties window.
6. Click on the Driver tab.
7. Under Current status, click Stop.
8. Under Startup type drop down switch the driver to Disabled.
9. Click OK

You’ll now have true silence from your desktop or laptop PC regardless of whatever crazy error messages pop up or however much spam gets delivered to your Inbox. Though this won’t help if you if you’ve got a bunch of 80mm fans running at 8000RPM still . But that’s for another post… Tip though, voltage converters for fans or fans with a high CFM and low dB rating work amazingly well as do rubber gromets for fans and HDD’s and not to mention that Dynamat isn’t half bad for noise absorbtion as well.

This is a common question on XP and even Vista. If you do a basic search with Google or Live you’ll actually get mixed information with many people (including some Microsoft sources) saying that sharing of networked content is not possible. However let it be known that it is possible and this information is available directly from Microsoft’s own sharing FAQ’s.

If you want to share files in a monitored folder that is located on another computer (for example, a folder on a network share), the remote folder must have the appropriate Windows access permissions assigned to it and the computer that contains the library you want to share has remote content sharing enabled. You can enable remote content sharing by performing the following procedure on the computer that contains the library you are sharing.

1.	Click Start, click Run, type regedit, and then click OK.
2.	In the registry tree (on the left), expand HKEY_LOCAL_MACHINE, SOFTWARE, Microsoft, MediaPlayer, and then Preferences.
3.	Right-click HME, point to New, and then click DWORD Value.
4.	Type EnableRemoteContentSharing, and then press ENTER.
5.	Right-click EnableRemoteContentSharing, and then click Modify.
6.	In the Value data text box, type 1, and then click OK. If you later decide to disable remote content sharing, you can repeat this procedure and change the value to 0.

For more information, see Windows Media Player FAQ.

I should also note that typically you need to make sure that WMP is monitoring the network share via the UNC path so \\SERVER\Music, while you can certainly have the share mapped to a network drive this will cause issues in certain cases. So if you add M:\ for example, make sure WMP is monitoring and using \\SERVER\Music instead. Issues that come up include the networked content showing up on first use but not being able to play back, and after the machine starts the content not being up to date. For more info check out this post.