(Another double feature!)

Part I: Top ten reasons why Dial-a-fix doesn't support Vista yet

10. Vista sucks
9. Vista sucks
8. Vista sucks
7. Vista sucks
6. Vista sucks
5. I don't have very much personal time available to me these days.
4. I don't have any spare computers with which I could run Vista at the moment.
3. I use Borland Delphi which is fucking terrible, and I haven't been able to get back to my C studies for several months now. Object Pascal (as a language) is kick-ass (in my opinion), but Borland's IDE is complete garbage - especially its cost. Don't suggest .NET... that's not even funny.
2. Microsoft changed nearly everything Dial-a-fix is capable of fixing to the point that Dial-a-fix has to be rewritten from the ground up just for Vista. Nobody's really got lists of "common" fixes the way XP has. Dial-a-fix is just a collection of known fixes, anyway - 99% of what DAF does is not even my invention.
1. Microsoft should fix their shit so Dial-a-fix need not exist. Is it too much to ask for a brand new operating system version not to bring 7 years worth of bugs with it? Basically, #1 is that I can't currently be arsed to fix their brand new old bugs - that's their fucking job!

Everyone should petition Microsoft to get their shit together. How can this stuff happen so much to so many people that a program like Dial-a-fix needs to be made? If I can do it, why can't Microsoft?

I will probably make a Vista version, but don't ride my ass about when and where.

Vista is an abomination and it just goes to show you that even if you "listen" to your customers (by way of usability tests, etc) it doesn't guarantee you'll get the implementation right. Microsoft needs to go back to the basics and re-think the way people use computers. Most people are multitasking, non-deterministic users. Some are single-tasking deterministic users who have old habits that are hard to break. Tough for you folks - you'll need to renew your computing license. One of the problems I see in Vista is that it tried to simultaneously retain backward compatibility while moving forward. The result: a train wreck. You know who doesn't care AT ALL about your previous programs working? Apple. They couldn't give less of a flying double monkey fuck about your programs working in the next version. You know what else? This seems to be perfectly acceptable behavior in the Mac community. Why isn't anyone up in arms about how Apple constantly ditches everyone, each time a major OS release is made? At least Microsoft tries (even if they inevitably fail).

Part II: Mac zealotry

Don't even get me started about Mac zealotry (too late). Some (but not most) Mac users have serious mental issues and honestly believe that Apple computers are somehow special or better than PCs. I have news for you: they suck exactly as much as PCs - no more, no less. They fail too, and often in the same ways as PCs. Sure, there aren't any major viruses going around, but that's because people with virus programming skill are usually in it for the money, and are too skilled to waste their time on 1% of 1% of the computing population. (It might even be embarrassing to them to some degree.)

Apple almost had it right except that they've spent a lot of their time and money mocking Microsoft Windows and not a whole lot of time developing a better computing attitude and environment and moving forward with technology. So what if you're some hipster/yankee twentysomething who buys vendor-locked brand name computers at ridiculously inflated prices to use most of the same programs that are available for Windows? Sure, sometimes it's not the exact same program, but with so many choices available, there has to be something for Windows that does the same thing as what you're trying to accomplish on a Mac. There's a lot more freeware on the PC than there is on a Mac, too.

Most of the time they mock PCs for the wrong reasons. PCs don't get viruses, Windows does. PCs don't need major overhauls to upgrade operating system software - Windows does. A PC is just some hardware. Everything after that is up to the operating system, of which there are many available. It's just unfortunate for all of us that Microsoft won that war before the war really began.

You know the Mac guy on the PC versus Mac commercials? That guy is more smug than a motherfucker. Meanwhile, the PC guy is hilarious and has a nerdy charm to him. The Mac guy is a huge douche about everything, constantly mocking the poor PC's troubles, ignoring the fact that he has his own, as well as the fact that he lives in his mom's basement smoking pot all the time and needs to shave, get some respectable clothes, and get a fucking job.

I digress.

You basically bought a PC with different software on it. You have what kind of processor and motherboard (I'm sorry - "logic board")? Oh right, Intel. What kind of power supplies are used in Macs? ATX and BTX. What kind of hard drive? Seagate. Congratulations: you bought the most proprietary PC possible that still contains nothing but regular modular PC parts (excluding the motherboard's design and firmware). At least it can run Windows, I guess. I'm not sure if that's a pro or a con.

(This is going to be the longest blog post I've ever written.)

Hello all. I've been away for quite a while. I have been put in the position where I work as hard during personal time as I do during actual work time. In fact, going to work is a bit of a relief to the life part. As such, I have not done any development at all on Dial-a-fix and I am very sorry. Vista support is long overdue (as you can see in the message you get when you try to run Dial-a-fix in Vista) but I have just not had the energy to complete this overwhelming task with my remaining personal time. Vista changes the way *everything* works to where Dial-a-fix is no longer able to perform the same tasks. For instance... I know someone who wanted to fix System Restore and was not able to make use of Dial-a-fix because the operating system is Vista. Unfortunately, in Vista, System Restore is no longer System Restore - it's more of a function of the Volume Shadow Copy service. So you see, I have no idea how that shit even works now. It's not the same at all. At least 50% of the DLL registrations don't even exist anymore. Most of the checkboxes would go away. Windows Update is now a program and a few services so I don't really know how that works.

I have not answered my email box for a couple of weeks, either, so I apologize if you wrote to me and I did not respond. You can try posting in the DjLizard.net subforum at Lunarsoft.net forums and hope that Tarun or others can assist you or wait it out for me to eventually get to you.

Below this line is where the long story begins...

Read more

Does anyone know why Dial-a-fix sometimes gets an "unspecified error" while trying to unregister MSXML3.DLL? It seems to be new because it's never done that in the past. Apparently you can immediately try it again and Dial-a-fix will then be able to unregister/re-register it. It's weird.

(Update: see the comments for a possible explanation. Short version: just run the same parts of Dial-a-fix again and you shouldn't get the error. If you still have trouble with Windows Updates, try clicking "Flush SoftwareDistribution".)

Superfail part 1
Superfail part 2

Thanks to astute reader Nate Coffey and Dial-a-fix, we've found another DLL registration bug.

The current version of wuaueng.dll provided to Windows 2000 service pack 4 clients has a bug in its DllInstallServer.

In the first picture is a "before" screenshot that shows that all of the SvcHost key values are here. This is a freshly installed Windows 2000 machine that only has Service Pack 4:

Everything's normal

In this second picture, I have visited Windows Update, gotten the latest Windows Update client, closed my browser, and then unregistered the DLL using regsvr32 /u:

Where'd it go?

In this third picture, I have re-registered the DLL using regsvr32 /i, but it caused an error (0×80070057) and only one key was put back. The netsvcs key is lost at this point. In order to fix this, merge this default SvcHost key .reg file.

DllInstallServer is broken.

The error code 0×80070057 is E_INVALIDARG, or invalid parameters/arguments.

The current version of Dial-a-fix will accidentally trigger this because of the malformed DllInstallServer in wuaueng.dll. Once a new, fixed version of the Windows Update client is pushed out, Dial-a-fix will be able to help you again. I'll be filing this as a bug with Microsoft - I hope they fix it.

Edit: be sure to read Superfail part 2 for the solution for afflicted machines.

http://forums.techguy.org/all-other-software/609118-solved-dial-fix.html

Basically Dial- a fix .. Does nothing .... Very few cases .. it solves the problem

...and this gem...:

All this can be easily achieved by a batch file

I've seen stuff like this floating around the web before. It doesn't really faze me as it just proves the poster's ignorance.

Dial-a-fix started as a set of batch files which were long and ugly like devil_himself's list of DLLs. Batch language differs slightly between Windows versions, and so do DLL registrations. Obviously, Windows 9x can't register all of the same DLLs that Windows XP can. IE7 also changed a lot of DLL registrations.

After a few months of using multiple batch files for each issue set (Cryptography, Windows Installer, etc) I got tired of having to fix them whenever a new conditional interrupted the workflow (such as a new version of a DLL that is no longer registerable, or to add dependency checks for missing files that I didn't realize could be missing when I first wrote the batch) so I converted the entire project into actual compiled code. This way, I could use real logic instead of a weak batch engine, and support more platforms.

The main problem that I have with that thread is that the junior member penguin47 has said that Dial-a-fix has solved the problem and simply wondered how it works. I wish he had asked me or Lunarsoft.net, but what can you do? Fortunately, the "senior member" devil_himself let him/her know that Dial-a-fix does nothing at all and has implied that it can accidentally fix your problem sometimes. I love that at the end devil_himself stated that this can all be easily accomplished with a batch file. Did you expect penguin47 to have found or written one?

penguin47 found my program, and it fixed the problem easily - for free. What's so wrong with that? Sure, you can easily write a junk batch file that does similar things to Dial-a-fix, but why would you shit on a program that makes it ten times easier and works on multiple versions of Windows, checking for stuff your batch file could never check for? My guess is that devil_himself is not an actual bench technician or has never used Dial-a-fix. I can't imagine any other reason to avoid something that is free and works this well just because you have some kind of batch file pride.

Yes, Dial-a-fix tells you all of the basic commands necessary to perform the same operations (somewhat) in its tooltips but you must remember that there is not enough advanced logic in a batch file to match what Dial-a-fix does now (checking for dependencies, etc).

http://www.maximumpc.com/article/broken_windows_fixed_quick_with_dial_a_fix

How did I not notice that Dial-a-fix was mentioned on my FAVORITE no-bullshit magazine's online blog-thingy-or-whatever-the-fuck? Oh yeah, I don't have an up-to-date subscription and I don't read the online stuff of theirs, but I guess I need to start.

Click the Digg button once you get there. Then, cross-post on Slashdot so that the internet explodes.

This is the best review of Dial-a-fix I've ever seen. It's very clear that Mark Soper understands what Dial-a-fix is about and what is going on under the hood. Thank you 'Marcus Soperus' for your kick ass review.

Speaking of Dial-a-fix — I need to get to fucking work!

...because of that PC World article.

You guys better donate me some moneys!

Digg it here.

Then you should read this post and visit this forum and post and your issue there.

I've had two replies today that I could not deliver because of one reason or another.
Red Condor was unable to deliver the attached message to Bruce Dawn, and Barracuda Spam Firewall could not deliver to Jim Remy of deltagraphics.com.

I forgot to mention this before:
http://www.pcworld.com/article/id,137083/article.html

That's in contrast to his previous article where he ripped me a new one:
http://blogs.pcworld.com/tipsandtweaks/archives/002591.html

That's okay though, I used that as motivation to consider how best to present the interface to end-users. It didn't really work out in my favor, yet. I'm working on making Dial-a-fix more user-friendly now.

Also, Steve Bass is hilarious.

Haven't gotten a chance to work on Dial-a-fix for most of this month. Real life duties, etc.

At least I changed the theme. I hope it's well-received.

Next Page →