in

Blog By Bob

Blog by Bob

August 2005 - Posts

  • Bob the Retard, or Why Was I Installing IIS Again?

    Ok, so below I was trying to hack IIS into Longhorn, well, after some research, it seems that IIS is already there (doh!) and you just need a couple steps to use it.

    Start|Run type services.msc, open the property pages for Web Publishing Service and change this to automatic and then start the service.

    Start|Run type inetmgr and this will open the IIS snapin...

    Thanks for playing, please drive through...

  • Channel 9 and Don Box

    I really enjoy watching many of the Channel 9 videos, and Don Box is the man ;)

    Watch the video

  • Microsoft 'Support'

    Outsourcing has definitely helped Microsoft's support, well, I shouldn't say that, many aspects of their support hasn't really changed at all.

    My automatic updates attempted to install 'Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903)' but failed, I tried to go to Windows Update and manually choose and install it and this failed as well. I see a link there to contact Microsoft Support if you have issues with the Windows Update Site, so I decide for curiousity sake to click it.

    I fill out a very detailed error description, giving both the update I am trying to install and the error I recieved, I state that this is one of 4 updates Windows Update tried to install, the others installing correctly while this one failed, and mentioned both tries at install.

    The email I recieved in return humorously explains to me in a 3 page form letter how to get the Active X control needed to run Windows Update installed and working...

    I am starting to see where Microsoft could cut some costs...if you aren't actually offering me support then remove the link and the phone numbers.

    Sure, the answer is most likely as simple as downloading the actual exe for the patch and installing it myself. I wasn't looking for a solution, but was curious what someone would get had they been.

    Thanks Steveb for not letting me down again ;)

  • Add Remove Windows Components and IIS Longhorn (Vista) style

    So, you saw the screen shot of Add/Remove Windows Components working on Longhorn. Now for alittle more information on getting this working.

    The first thing you'll need is several files, this first list is geared towards installing IIS, but will give you enough information to copy the files you need for any other components as well. Before you get too excited, no, I don't have IIS working. IIS 6 installs but is missing one or more dependent services, and I haven't had time to sort them out yet, but wanted to get this post up (who knows, one of you smarter people might finish that part for me).

    You will need a machine with Windows 2003 Server installed, or the install disk if you want to manually move the files out of the install cabs. Add/Remove Windows components will also work from XP, but IIS 5.1 does not seem to like Longhorn at all.

    From the system32 directory you will need ocmanage.dll and sysocmgr.exe

    From the system32\setup directory you will need the IIS.dll file (the other files can be copied across to have other options besides IIS in the Add/Remove menu.

    From the system/inf folder you will need sysoc.inf/pnf and iis.inf/pnf (I don't know if you need the pnf files or not, but they are small and liked being copied, so I obliged...)

    Open your sysoc.inf file and remove all the components entries except the one for IIS (this of course would be different if you wanted to install other components and 2 exception I found to installing other components were the dtc and inetprint lines which still break even copying the whole system32\setup folder. They may be located else where or not, but they weren't my concern so I just deleted them).

    At this point, you only need to click Start|run and type in sysocmgr /i:sysoc.inf (thanks Seth!) to launch the Add/Remove Component snap in.

    I will most likely work on IIS further this weekend, IIS 6 seems the more promising for several reasons.

    • Since the WinHec build, Longhorn has been based on the Windows 2003 code base
    • IIS 6 installs, though it sometimes stalls during install and just needs installed again, but is missing dependent components, which should be easily enough remedied
    • IIS 5.1 complains it can not be installed on an OS other than XP or greater (I would have thought Longhorn was greater...). I tried removing the OS dependency in the iis.inf file and that did not help. I tried using the 2003 server iis.inf file with the IIS 5.1 iis.dll and still saw the same behavior, so it would seem to be burned into the dll itself

    Good luck, and if anyone gets IIS working, let me know!

  • SPAM!

    I couldn't understand why I was not getting any mail, I usually get a ton, until I noticed Outlook Express got a spam filter in Longhorn. A nice, if late, addition. Yeah, I know, I need to get off my behind and install Office for Outlook, and I will, as soon as I get IIS working ;)
  • Add/Remove Windows Components on Longhorn

    It wasn't easy but here it is...

    More info on how to do this tomorrow, I want to clean up my notes and it is all late and whatnot. I think I might be able to get IIS working this way, as this was my goal in starting. When I choose to install IIS on Longhorn, it asks me for my Windows XP disk, so it looks like it may let me install IIS 5.1...

  • A Day in the Life of IE7

    So, I decide to give IE 7 a spin, considering how much I bitched about a new version of IE. I double clickity click and of course, since I use a real OS (Windows 2003 Server) it won't install. I decide I really didn't want a new IE anyhow...

    Just kidding. I happen to run Media Center on the machine in the living room, so I copy the install on it and launch away. It wants me to authenticate my windows install, to make sure I am not an awful thief. I have no concerns about this, my MSDN subscription keeps me in good standings...until, it refuses to authenticate my install because I haven't activated Windows.

    There is a slight dilemma in this course of action. This beta is an MSDN download. As an MSDN subscriber, I am brutally aware that I am only allowed 10 activations per product that requires activation. (or so is the theory, I never activate Windows so I don't know for sure)

    Hence the dilemma. Microsoft specifically tells us not to activate our product unless we plan on having it installed for more than the 120 days of the MSDN activation window. Now with IE7 as well as the new Windows Update, we are required to activate Windows before receiving updates. I would be 10 times over my activation limit if this had always been the case.

    Look for Microsoft to have to end the activation limit on MSDN subscribers, assuming they haven't already.

    So, I activate Windows, accept the licensing stuff, click next, next, etc. BAM. The installer has caused a problem and needs to be closed. Beta product, no worries. I reboot and it is working fine.

    I figure I will check what other updates might be available and head to Windows Update. Which hangs. Forever. After some quick reading, this seems to be the rule, not the exception. I remember similar issues with Windows Update on SP1 beta for Windows 2003 Server, so no real worries, even considering last I looked, you still couldn't use Windows Update in the 64 bit version of IE...which has been out several years...well, in computer time anyhow.

    We'll look at some of the interface options first.

    It was a nice surprise to see you can choose other search options besides just MSN (you can choose Google, Yahoo, MSN, Ask Jeeves or AOL search)., though the one option I actually wanted wasn't there. You can't just get rid of the damn thing. Google is, and has been for years, my home page, I don't need a search bar in my browser.

    After I got past that, I noticed what many others mentioned about the File|Edit menu being below the address bar and the tabs. I actually kind of like it there, but there would only be one question to be asked. Is this going to be the way of Longhorn? Nothing is more important in an operating system, or in any application than a consistent interface. If this is not consistent with the rest of the OS, then dump it.

    The next thing I noticed was the RSS reader. I know alot of people have been into the RSS thing for quite some time now, I am not so quick an adopter, but I did find the RSS reader incorporated in IE 7 to work well, and be easily used by one with such limited knowledge as myself.

    While looking at the RSS Reader, I noticed a link in favorites for Internet Explorer Add-ons. I am not going to go into much detail here, but suffice it to say there is a nice variety of addons available already, similar to the nice level of addon support Firefox users are used to. The one thing I will mention, is a plethora of download managers, mentioned because this seems to be one of the things alot of non IE users hate about IE.

    While we are on the interface, lets talk about tabs for a minute. The tab implementation, in my humble opinion, shows great promise, but was left half done, and so sucks. I don't know how I feel about the little 'nub' of a button that launches a new tab, many people hate it, I don't hate it, I just fall back on my previous statement about consistent User Interface. I do wish the new tab would open as my home page, instead of as about:blank. I am not sure where I want to go with my new blank tab, but going to my home page (Google) is alot more likely my destination then going to about:blank. My only other comment on the tabs is having to click an X on the OPPOSITE side of the screen to close them is about the most retarded thing I have ever seen in my life (Hello Steveb?). I know you can right click and choose close, but that is not a well flowing answer either. Either they should incorporate an X into the corner of each tab, or as a shortcut, double clicking a tab should close it. I lean towards an X in the corner of each tab (people who use GAIM will be familiar with this).

    Last UI note, where the hell did my refresh button go? Yeah, I know I can just hit F5, but when in the living room, I may or may not have the keyboard near me, with everything being wireless, so sometimes it is easier to click refresh...

    I know I spent alot of time on the flashy part (the UI) and no time on the important parts (standards, security, etc), but that is because the UI changes are all I see. It seems so far the only standards work they have really done is fix 2 CSS bugs, and the default settings for security is a step back from Windows XP SP1, albeit the addition of 'phishing' as a plug in gave me a nice laugh.

    We've collectively as a whole asked Microsoft for a browser. We have waited so very patiently. We have received nothing. Ask them to take back this sorry excuse for a pacifistic attempt and come back when they have something to provide. I know there is much time left before IE 7 comes out in force. Much time to do the things that haven't been done. Beta 2, RC 1, RC2 etc, but it isn't that fact that disturbs me. Its the fact they did the UI first, the part that is easy. The part that can sometimes make people forget what is behind it. They say don't judge a book by its cover, but it seems by this release, Microsoft is hoping we will. I was going to install Longhorn this evening, but after looking at IE 7, I don't think I will bother.

More Posts
Copyright © :: BlogByBob.com
Powered by Community Server (Non-Commercial Edition), by Telligent Systems