in

Blog By Bob

Blog by Bob

May 2005 - Posts

  • Site outage

    One day, most likely this weekend, the blog will be done for part of a day. I've changed jobs and in the process am moving from Charlotte to Greensboro, so I will be moving the servers. So if the site doesn't load, don't fret, I haven't gone anywhere ;)

    As to the job, it has me super excited, it is the kind of thing that I think will keep me excited and entertained years. An awesome place from everything I've seen so far and awesome technological opportunities.

    The only down side is I will be working with Ray...;) just kidding bro :P

  • Remind me to email steveb...

    All my other emails to steveb have been about security and IE for the most part. This next one is going to be about Office 12, not just a request for features but for some reason it seems my beta copy hasn't come yet. He hasn't replied to any of my email messages lately, I hope his spam filter isn't accidently filtering my emails...You can get some information (what little is out there) from here.

    To:steveb
    From: El Roberto
    Subject:Office 2006

    Good morning Steve!

    I have been reading about the next version of Office with much excitement, and wanted to add a couple of comments about items that may help with getting people to upgrade. I know during every release you fight with the 'what I have is good enough' mentallity and anything I can do to help you bring the masses to the next level, I am more than happy to assist with.

    Some of the things I would personally like to see come down the pipe with Office 2006 are

    1. More XML compliant on the back end. I understand the want to keep your data formats proprietary, but this is no longer viable. Consumers *want* to be able to use threir documents in whatever application the feel like. The 'other guys' are going to reverse engineer your formats and allow their apps to read it any how, so quit being a pain in everone's ass and just play nice. The consumer is the target audience here, and as much as most of them may not even know it, they want this feature.

    2. WinFS should be out by the time the next version of Office comes out (yeah, I know, this is probably a 50/50 with Microsofts track record with WinFS). I would like to see some components rewritten to work seemlessly with, really integrated and not hondge-podged together as so often happens when Microsoft 'adds' features.

    3. Give me a decent spam filter. The one in Office was a good start, I am not going to deny that, but it quickly became something that was easily defeated. Gives me something that isn't so linear and is more componetized and can be replaced/expanded over time.

    4. Include One Note with Office. One Note is *the* bomb. One Note is an awesome application that would be even cooler if it were to get some mainstream attention. The kind being included with the new version of Office would provide.

    I think that is it. I don't think 4 things are such a demanding list. I do think some of the things I have seen listed as 'going to be included' are nice, like some of the new tools that help you manage information flow and manage the data sources it comes from.

    I know you are a busy man, and I will let you get back to whatever you were previously doing. I did notice, if you have the time, I haven't recieved my beta copy yet. If you could send off an email and check on that for me, I would owe you a big one. Stop by and have a look at the blog, I hit 100 posts the other day ;)

    Bob

  • Paperless office...

    Well, the paperless office is still a myth, but it seems Microsoft is finally trying to do away with the 'paper mcse', which eventually had to happen anyhow. Microsoft's premier certifications have become such a joke, that it is often times better to *not* list them on your resume so your prospective employer thinks you may actually have some experience, rather than spending all of your time reading books with no relevance what so ever to anything except passing the specific test you are taking.

    Hell, look at me as a perfect example. I have MCSD in both 6.0 and .NET, MCDBA in both 7.0 and 2000, MCAD and MCSA. I dont even know how to tie my own shoes, or what half of those abbreviations mean. I think they have something to do with donuts...

    Well, not really, but I am glad they are addressing this issue, it is a pretty serious lacking in their certification program, I just hope they roll it out across the board once they get the networking pieces worked out. The MCSD track is *way* easier than it should be, it should be proof you can write enterprise level apps, not proof you read 3 silly little MSPress books...

  • 100th Post

    I was going to say something cool for my 100th post, but then I realized I havent said anything cool yet.....
  • Firefox is dead, long live Firefox

    So...several people told me of the wonders of Firefox, and I even tried it, honestly tried it, for about 2 weeks. Everyone talked about how wonderful it was and about how secure it was...yada...yada...

    Suddenly I don't hear them anymore. Looks like they have a long way to go to even get to the point of being as poor as IE 6. They look forward to Firefox 1.1, I look forward to IE 7.

    Copy and Paste with a link:

    Zero-Day Firefox Exploit Sends Mozilla Scrambling

    For the fourth time in three months, major security flaws in the upstart Firefox Web browser have pushed volunteers at the Mozilla Foundation into damage-control mode.

  • XBox 360 specs

    There is a rather heated, well heated for us, conversation going on at Jayson's blog about the rumored specs on the next iteration of the XBOX. Head over and add your 2 cents, none of our comments are worth more than that...

  • SQL Server SP4

    So, I noticed that Microsoft released SP4 for SQL 2000 without really telling us, and I went ahead and installed it on a couple of my SQL machines, bringing their build numbers to 8.00.2039. So far this looks more like a maintence rollup more than anything else. Impressions so far? Well, it was nice they fixed some issues with SQL 2000 running on native x64 platforms, even if they didn't make it actually run in 64 bit. It is bad that they didn't fix Reporting Services so it would work in that environment, but considering how much of a hack Reporting Services is, I am just happy they can get it to work on anything. Anyhow, bitterness aside...

    The first thing I noticed, on the first machine I installed it on, the SQL Server services did not restart after completing the installation of Service Pack 4. This was not repeated on the other machines, so most likely I just did not reboot after the install. I really am not real big on rebooting...

    The installs themselves went very smooth, SQL Server seems to behave the same as it did before. I don't have SQL 2000 on my 64 bit machine, I have SQL 2005 on it, so I can't speak to that.

    They spoke of 'GUI Enhancements' as well as other things, but what I saw I would not necessarily consider enhancements.

    As you have surely noticed, when you return a result set in Enterprise Manager and then wander off to get a Dew, upon returning, SQL is threatening to clear the result set because you aren't playing with it anymore. They have update the wording on this and it now looks like this:

    The next thing you'll notice that is new, is if you right click a table and choose Design Table, larger tables now 'warn' you that it might take some time to save the changes to the table's schema...well, duh.

     These definitely are geared more towards beginning users and not SQL DBA's who do this as a living. I guess they are just following the pattern of everyone else, targetting the least common denominator. To see another example of this, head over to Borders and see how many books are 'technical' compared to the number of For Dummies books and How to XXXX on Ebay...but I digress into my bitterness again.

    The only 'issue' I ran into, I had some recollection of possible GUI changes in the Database Diagram thingie, so I went in and played with it, but it looks pretty much the same, I did however get an error trying to create a database design on one of the databases.

    After receiving this error, Enterprise Manager had to be closed and reopened or I would get this error everytime I tried to create a diagram. All in all it appears to be a safe install...'appears', so don't come yelling at me when it hoses your box...

    Oh, and unlike Ray and Mike's comments on my last post about SP4, I actually like having an improved BOL, what coder doesn't like better/more documentation?

  • Virus FUD

    I am tired of FUD, the latest being this huge 'OMG, 64 virus death evil' something or another. Everybody is talking about Norton, McAfee et al not offering a native 64 bit version of their antivirus software, and how 64 bit early adopters are going to be consumed by this new wave of viruses aimed at them.

    My reply? Get a real virus vendor, they have had x64 native support since before Windows x64 went RTM, and quit spreading your lies. This is almost as annoying as the paranoia over cell phone viruses.

    It is sad to see most online journalism is becoming(has been?) nothing more than online tabloids, no more accurate in content than the National Enquirer. And the blog explosion isn't helping with this, how many people actually check the accuracy of posts before assuming them true? Maybe Seth was right and blogs are evil.

  • Blogshares

    I can't decide whether I like Blogshares or not, I think that I would like it better if my stock was worth more... It just hit a dollar, everyone go buy some while you can afford it ;) Come on, help a brother out, I need to stay higher than Jayson!

    *UPDATE* Better hurry, the stock was in 61 cents yesterday and is nearing the 4 dollar mark a day later *UPDATE*

  • SP4 for SQL Server 2000

    Seems Microsoft snuck out a Service Pack 4 for SQL Server without really telling anyone. At least noone I know was aware of it. It appears to have come out on the 6th. You can get the download here.

    Quick copy and paste of the new stuff:

    SQL Server 2000 SP4:

    • Includes a new version of MSXML version 3.0 SP6. With SP4, the OPENXML statement is updated to use a custom-built XML parsing technology designed to be backward compatible with MSXML 2.6.
    • Includes MDAC 2.8 SP1 except for Windows XP and Windows Server 2003 platforms, where it is included with the operating system service packs for those platforms.
    • Adds the following platform support:
      • With Microsoft Windows Server 2003 x64 Edition, SP4 provides support for 32-bit SQL Server applications on 64-bit architectures using the Windows on Windows emulator (WOW64). For more information on specific 64-bit platforms supported, see the Windows Server 2003 x64 Editions Product Overview.
      • With SP4, you can leverage 64-bit processor architectures using 32-bit SQL Server applications when running in WOW64.

        Note: SQL Server 32-bit applications, including SQL server client tools, are still not supported on WOW64 for IA64. Also, currently 32-bit Reporting Services is not supported to run on WOW64 on IA64 and x64 platforms running Windows Server 2003 x64 Edition.
    • Improves documentation; the Readme documents are reorganized into four distinct readme files for the different SP4 components:
      • ReadmeSql2k32sp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 (32-bit)
      • ReadmeSql2k32asp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 Analysis Services
      • ReadmeSql2k32desksp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
      • ReadmeSql2k64sp4: Readme for Service Pack 4 for Microsoft SQL Server 2000 (64-bit)

    This brings the build number to 8.00.2039.

  • Microsoft's push for 64 bit

    So, I have Windows 2003 Server x64 installed and am off to install SQL Server. I didn't realize that the only 64 bit version of SQL 2000 is for the Itanium, oh well, it isn't like I am not a beta freak, so I go to download SQL 2005 x64 CTP...

    I get the 'There was an error launching the File Transfer Manager' that we've seen since XP SP2/2003 SP1. I tell it is ok to install....and I get the 'There was an error launching the File Transfer Manager' again. Seems their control isn't compatible with the 64 bit version of IE.

    I know I can just launch the 32 bit version of IE and it will work fine, but damn, if they want *us* to adopt 64 bit, shouldn't they be alittle more passionate themselves? Especially on the MSDN site, I would suspect there are more developers than anyone else running x64 at this point in time. I think its time to have another talk with steveb...

    Speaking of steveb, someone pointed out something humorous to me the other day. If you go to MSN Search and search for 'steveb@microsoft.com' , my site is the second entry, beaten only by his PressPass link...

  • DeDupe in SQL Server

    One of the things I have to do often at work is dedupe a file based on one or more fields. There is alot of sample code out there to do this, but for what I usually need it is pretty complex. Now, I don't profess to be a SQL Person per se, but below is a clean, simple psuedo sample I use often, and it seems to work pretty well.


    declare @DUPEKEY int
    declare DeDupeCursor Cursor

    for
              select distinct dupekey from sourcefile
              open DeDupeCursor
              fetch next from DeDupeCursor into @DUPEKEY
              insert into destinationfile select top 1 * from sourcefile where dupekey=@DUPEKEY order by OrderKey desc

    while @@FETCH_STATUS=0

    begin
              fetch next from DeDupeCursor into @DUPEKEY
              if @@fetch_status=-1 break
              insert into destinationfile select top 1 * from sourcefile where dupekey=@DUPEKEY order by OrderKey desc
    END

    close DeDupeCursor
    deallocate DeDupeCursor

    Surprisingly .Text even formatted it pretty well for me, considering how badly it mangles copy/pasted C# code...I am sure there is a way to get rid of most of the first block, but it works well enough that I haven't really pursued it. And for those that think using a break in a sql loop is evil, well, I don't like you anyway...

    We won't get into any householding type solutions, my fingers would get tired.

  • Longhorn Revisited

    After having Longhorn 5048 installed for well over a week, I thought I would go back and cover Longhorn again, and see how my thoughts had changed since my first impressions. The first thing I have to say is Longhorn is super stable, which really isn't expected in an Alpha product, however I am sure alot of that has to do with the fact it runs on the Windows 2003 Server SP1 code base. I hear alot of noise about people who are disappointed in this build, that there are so many missing parts still, but it has to be taken into consideration that this build was released to allow hardware manufacturers to get some stable drivers built so the beta releases could focus more on the things wrong with the beta version of Longhorn, and less on hardware not working or not being supported. New Windows builds aren't supposed to be feature complete until RC1, and we are still a month or more away from Beta1. Having said that...

    The first thing I would like to do is go back to some first impression statements I made that may have been less that accurate. The first being Longhorn won't install in Virtual PC, this was only partially accurate. To get Longhorn to install in VPC, you have to have a VHD that is already partioned or formatted. Should you install in VPC now? No, you will be very unimpressed. It is more VPC's fault then Longhorns. Virtual PC doesn't replicate your base hardware, it emulates some basic hardware, a SB16 soundcard and a Rage128 video card for example. These devices are hardly Longhorn material. You *may* have better luck using the same proceedure to install Longhorn in VMWare, I may be mistaken as its been a long time since I used it, but I believe it replicates your actual hardware up to the virtual machine.

    The second statement that needs clarification is that there was no link to Services from within Administrative Tools, this is still true, however Seth informed me after much ridicule that you can still get to the Services snap in by typing 'services.msc' from in the run dialog. I also said IIS is not available, which it seems the bits may be there to activate if you could get the Add/Remove Windows Components, which is also not functioning. Master Seth wasn't able to tell me the command line to launch that snap in...

    Now to some of the quirky behavior. The first thing I noticed, since all my install packages are on the network, is that network browsing is very, very slow. Both getting the original window to open and moving from folder to folder. This may be a side affect of ripping out WinFS, but I assume it has more to do with Longhorn offering alot more metadata information on files than XP. I assume this will be smoothed out for Beta1.

    The next item set a trend for some other similar issues. I installed eTrust antivirus on the machine, but Longhorn didn't recognize it as having antivirus, which is fine, this is an alpha release...However, I chose 'I have antivirus installed that I will monitor manually, the warning went away. For two reboots. Then Longhorn told me again my PC was not protected because I didn't have antivirus installed. It lost the setting every two reboots. This may have been the behavior in Windows XP SP2 and Windows 2003 Server SP1 since I never ran either without antivirus, but somehow I have my doubts.

    This amnesia also affected the Language bar in Office 2003. Office itself worked wonderfully, but I dont like the language bar in the task bar and turned it off. Ever couple of reboots it would be back. I turned it off 13 times, and interestingly enough, after that it seemed to go away for good. Odd to say the least. GAIM had a similar issue, but only once. I changed all the settings to my preferences, then one reboot several days later, everything was back to the default settings, but it still remembered all of my account information. This only happened once though, but I never saw anything similar from GAIM in Windows 2003 Server.

    All things considered, this is a mild, mild case of quirkiness from an Alpha OS build, but the one thing that killed it for me was not being able to get my wireless working. Ever since build 4074 when I turn on my built in Broadcom wireless card, the OS would hard lock until I deactivated it. I have USB wireless card as well, but the driver doesn't install in Longhorn, and I have no desire to buy wireless cards until I find one that works.

    So, what's the next step? Well, I am kind of jealous that Tristan has more bits than me, so the box is flattening as we speak and 64 bit Windows 2003 Server is installing....yes, I am a glutton for punishment.

    I am sure I will have comments on this OS soon as well, and I look forward to trying the hack that is supposed to allow you to run 32 bit ASP.NET apps on the 64 bit server. Fingers crossed as that is a deal breaker if I can't run IIS, since in the RC builds Virtual PC would not install, and even if it *will* install now, I have serious doubts about being able to install a 32 bit version of an OS inside of it.

  • New blogger

    Well, Seth has been threatening to blog for some time now and is finally up and running. I told him I would post a link here so he can have my 2 hits a day, so go over and say Hi, I am not sure what the contain will include, but knowing Seth, I assume it will be entertainingly technical...considering BOFH is his favorite site.
  • Interesting turn of events

    I was pretty excited the other day when I was handed my disc with Longhorn build 5048 on it. I rushed home and found out the same thing that alot of other people were finding out. 5048 doesn't install in VPC. I gave some thought to trying to install it in Virtual Server, not likely to succeed, but possible. The laptop I install on is my personal machine, but I use it for work, so putting a possibly quirky beta on the machine is not the best idea. Combine that with the fact the first machine Jayson put it on bluescreened half way through setup, repetitively and things look sorta dicey.

    So, I did what any other responsible computer professional would do.

    I flattened the damn laptop and installed Longhorn. What the hell, the activation period on my MSDN Windows 2003 server was almost up and I didn't feel like having to activate it.

    What are my impressions? Well, I hear alot of noise about the GUI being crap, and people defending saying the GUI is still ALPHA, or its a place holder or whatever. The GUI needs some work, that being said, alot of it is poor default choices. With some tweaking, the GUI in its current state or AEROness can look very nice. Much better than XP, not quite on the OS X level yet. I can see the potential though, and to me, that is the important part. There are still alot of things they are obviously working on, for instance, if you switch to details mode, the file name is truncated very short. You move the slider over so you can see the whole bar, and when you come back the next time, the name is truncated again. But, this is ALPHA, and I see the potential.

    Talking about potential, the navigation system for the browser and navigating windows has changed...almost dramatically, but not quite. It is the same enough that you won't have to learn again how to get around Windows, but different enough, that if you explore some, you will notice there are much faster ways to navigate then you could before. Also, for those that saw the older builds, rest assured they fixed the god awful ugliness that was the top of Internet Explorer. For those that have the current build, you will notice it is better, but if you choose View|Toolbars and the Lock the Toolbars to unlock it, you will notice you can drag that third row up with the second row, and I think the top of IE might actually take *less* space then on Windows XP in that configuration.

    I really, really wish I could show some screenshots to elaborate, but from what I have seen, that is a pretty big no-no at this moment, with this build. I can almost understand the reasoning behind this decision, but at the same time, it is somewhat surprising considering everything is about momentum. I would think they would want to capitalize on the current Longhorn momentum, but it is also possible they are just going to hold off for a month to let x64 breath and then get back on the Longhorn push.

    Enough about the UI, lets talk about stability and compatibility for a moment. I installed this on my laptop yesterday, so the stability part will mostly be premature, but I *can* speak to compatibility. The install found everything on my laptop except the video card and the wireless card, well, and the modem, but I dont install drivers for that anyhow.

    The video card was a quick download of the last Catalyst drivers and poof! done. The wireless I was somewhat concerned about. In 4074, whenever I installed wireless drivers for my Broadcom 802.11g integrated card, if I hit the function key to activate the wireless card, BAM. The OS would hard lock. Not crash mind you, just hard lock. Hit the function key and turn the wireless card back off, and the OS would continue on its merry way just as though nothing happened. Unfortunantly I am seeing the same thing in this build, no matter what version of drivers I try to install. Not a big deal, I am plugged in most of the time anyhow, and if I need the internet while not plugged in, I can stick a USB wireless Nic in for the moment.

    Well, once that was resolved, the next thing, of course, is to install Half Life 2. Have to get my Counter Strike on. If you are ever in a server and see someone name Bob that has 1 or 2 kills and has died....38823 times, that is most likely me. Say hi and try not to make fun.

    So, Half Life 2 installs, first good sign. I log into to steam and wait for the files to update. And wait...and wait. But that is a steam thing, not a Longhorn thing. That finishes and I launch Counter Strike. And wait for Steam to update. And wait. And wait...

    BAM! Begin game comes on. I arranged ahead of time and Mike and I are going into a server to wreak some havoc, he is going to shoot alot of people, and I am going to splatter my toon in many hallways. The game plays flawlessly for hours. Too flawlessly for too many hours. I am somewhat tired at work the next day. Anyhow, this is a very good sign.

    I have alot of things going on at work, but enough time I can click Next now and then, so I decide to see what else works. I install Visual Studio. NET 2003 and run into one of the first snags. It says 'Hello! Where is IIS??'

    I look around confused, because I haven't seen IIS for awhile. I ask around. I go to Control Panel and click on Add Remove Programs. I find and click on the Add/Remove Windows Components once I have changed back to classic view. Classis View doesn't really look like Classic View, but it actually looks nice once you collapse all the categories. Anyhow, I am playing with the categories while I wait for Add/Remove Windows Components to load. I click it again...37 times. Well, it seems there is no Add/Remove Windows Components in this build.

    I look around at another way to install IIS manually, but I don't think the code is there. Longhorn will have IIS 7 in it, so I am assuming at this point they have removed IIS 6 and haven't put IIS 7 in yet. I am really looking forward to another fresh rewrite of IIS if that is the case. I stop my Visual Studio install, becuase there is no real reason for me to keep Longhorn if I can't make ASP.NET applications on my laptop.

    On a whim, I decide to try and install Virtual PC on Longhorn. In an interesting turn of events, Virtual PC complains but installs and runs wonderfully on Longhorn, I install Windows 2003 server in a vhd and we now have a 'remote' IIS server to deploy to. Problem solved. Visual Studio 2003 installs properly and runs great.

    Next on the list is Office 2003 and Map Point. Both are tools I use often at work, and so far both seem to be working fine. For alittle less work related, I am somewhat concerned about installing Roxio DVD burning software and less so PowerDVD. PowerDVD installs and works great, emboldened by this, I slam in the CD for Roxio DVD Creator and reboot afterwards as asked. Works perfectly. So far things are going very well and I am pleased. If you have read some of my other recent work, you will know I am not often pleased. Anyhow...

    Some things I am still needing to install:

    Antivirus Software - I have and love eTrust, I will try to install it tomorrow.
    DVDShrink - A necessity of sorts.
    SQLServer 2000 - Work and whatnot, might install SQL 2005 instead, if others are successful...hey, I am only *so* bold
    Doom3 - I am sure this will work, given the sucess with Half Life 2, what I am interested in is with Windows 2003, I had to install Orca and remove the OS check from the Doom3.msi file. I wonder if the default file will work or if I will need to use the modified file.

    Some things that did *not* work:

    Shadowbane - MMORG that revolves around PVP (Player vs Player), may have been user error, I had installed alot of other things and hadn't rebooted, its not a priority at the moment, but if it installs later, I will add an update.
    Trillian - I use GAIM usually, but everyone claims it is inferior to Trillian, however, Trillian has never liked me. Ever. I decided with the whole fresh install, I would try it again. It installed fine but crashed while trying to log in. I pulled out my CAT5 and it ran fine, plugged in my LAN connection and it immediately crashed. Dont care enough to try again, GAIM is working fine.
    The language bar in Office 2003 - No matter how many times I turn this off, the setting never sticks and it comes right back after a reboot.
    \\machinename\share - This is blocked by default by the new firewall. Blocked *going out*. Not sure what they were smoking here, but I assume this will change by the time the next build comes out.

    I will update here as I install new things that may or may not be of interest. I really, really wish I could post some screenshots, but you know how it goes. Before installing this build, had you asked me when I was expecting Longhorn to go RTM, I would have said May 2007, maybe July or August 2007. Now that I have spent some time in 5048, I can believe their 2006 claim somewhat easier. Oh, and per my norm, the new Recycle Bin icon is sweet...

    *UPDATE* Doom3 installs fine with the default MSI file, and for Roxio, it installed and launches fine, but I am having issues burning. I think the IMAP service may be stopped, but I cant find the Services console to confirm.

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