Typically when I have an iso file what I want to do is mount it as a DVD Drive, not spend 10 minutes burning the thing just so I can then read it on the same machine and in the process wasting a DVD and causing more environmental damage with the plastic. OK so that's useful if I take it to a different machine or need to boot from the disk, but that's rare for me now days.
Guess what, in Windows 7 you can burn a iso image to disk. Great, that's a nice touch, but you can't mount the thing!
One cool addition to Windows 7 is being able to create and map a .vhd (virtual disk) as a disk on the machine in Disk Management (I've not tried it yet apparently you can even boot from it freaky & cool!). Now tell me why can I do that and yet I can not attach a iso image file, that's massively frustrating.
What makes it really crazy is that when you download from MSDN you get .iso files, now even with Vista you have to go and get extra software to handle them. At least you can burn them easily in W7 but really, I should be able to download a SQL server 2008 iso from MSDN, right click and mount it in W7 and install it.
I store all the iso's I download from MSDN on a network share and access them as I need them. If I burn them to disk I just loose them, so the bulk iso storage works really well for me.
It's similar in Server 2008 R2, no option to mount the CD/DVD and by default the burn option isn't their either but then that's for the best really as I'd want the default install to be locked down as much as possible.
I did wonder if their was some kind of legal, patent, copyright issue around the iso image thing, but Hyper-V can mount an iso image to be use as a CD/DVD drive in a Hyper-V instance so why can't Windows 7 do that?
Please Microsoft give us the ability to mount an iso image as a DVD drive!
Until they do I'm sticking with MagicISO which works a treat and it's freeware! (Thank you MagicIso inc!).
I'm also hoping one day we see DVD drives that can do LightScribe or similar without having to flip the disk but I doubt we will ever see that (at least for a reasonable price!).
Like many others I've been trying out Windows 7 just recently.
My trial of it didn't start well with the MSDN version being available around the same time as the public release I mistakenly thoughts as a paying MSDN subscriber I might get it a little earlier but hey, I get to find out and fix any problems in my applications at the same time my users get to see the issues. Still at least my stuff doesn't eat your MP3's!
I installed a test version of W7 in a Hyper-V instance which didn't go all that smoothly either, first time around and I had to have a second go, but that might have been because I put the iso of Windows 7 on a NAS and a network problem may have crept in causing the installation not to find the files it wanted.
Next (I think) because I access my Hyper-V set-up using the Hyper-V MMC snap-in from my Vista box copy and paste doesn't work between the two machines so entering the product code and trying to paste the Url in to browse for the patch to stop W7 trashing my MP3's was painful. But hey, I should save my Hyper-V bashing for another day as I could go on for some time about that!
What really annoys me with W7 is what has happened to the taskbar.
Apparently I'm not alone. Don't get me wrong, I'm not against change and I like a lot of what's changed over the years in Windows, generally it's been for the better.
With Vista, XP and those before it I actually like the quick launch toolbar. I like it having small icons and I use it heavily (I have 18 apps in there). I also like the notification area, not massively but for a lot of applications it's perfect. Theirs a number of application I don't want in their and think they should live else where (like the ATI stuff, SmartStamp, OpenOffice QuickStart) but I can live with that.
In XP Microsoft gave us the collapsing notification area and initially I adopted that but ended up finding it annoying, the worst of which was with Outlook email notification as I had times when XP would decide it should hide it and then you didn't get to see it hence ignoring new email (OK so not a bad thing) or other times when receiving a lot of emails it would cause the notification area to shrink and grow which was really annoying and had a side effect on the running programs and made it difficult to hit the correct icon.
There is one big problem with the quick launch, toolbar and notification area in XP and Vista and it's this that I believe Microsoft are trying to solve with the redesign in Windows 7. The problem is you can't fit much into the default Quick Launch and Notification areas.
So the way I see it is you have two options:
- Go the Windows 7 route and redesign the toolbar FAIL.
- Make the toolbar 2 units high by default this works a treat for me!
Let me explain why I don't like the new Windows 7 Toolbar:
- The new taskbar is to tall way to tall. It's smaller than my current Vista taskbar because I have that 2 units high, but the height for 1 unit in Windows 7 is not far off the 2 unit Vista one, so that means when I set it to be 2 units high it's massive - stupidly massive. I'll explain shortly why I like the toolbar 2 units high.
- I've never liked the grouping option of the Taskbar. I see that's on by default again, you can switch that off, or to group when it's full.
What I also don't get is why when grouping is on and you only have 1 instance of the app do you just get the icon but when it's off you get the icon and the application name? Why not the icon and app name normally? Although if you do show the application title like we are use to it becomes ever more confusing as to how you quick launch an application.
Anyway, I can never find the running application I want when grouping is on.
- Theirs not really a quick launch bar any more, you can pin your applications to the toolbar instead. These are full height icons taking up a lot of space (width and height) and then when you launch the application guess what, the icon stays where it is looking just like the launch icon, except when you click it again it actually minimises the window.
Now some applications are slow to load, some get messed up and load outside the screen area or minimise incorrectly/badly on start-up or go straight to the notification area on start-up you could end up in a big mess figuring out what's going on with the W7 way of taskbar launching.
And if you've launched an application from the taskbar and want to start a new session of it (say you want another IE 7 because you've got to many tabs open in the current IE7) it's really not obvious. You have to right click the icon and then choose the application name from the menu. novel!
- The notification area, if you use it correctly it's great and sadly some apps abused it. Now for something like Dinner Timer Lite you really want that icon showing so you can send the running Dinner Timer Lite instance to the tray and hover over it to see how long you've got left quickly and easily, not click an up arrow then hover.
Other application change colour or blink to inform you of things, this can be really useful, sometimes the icon changes such as when you mute the speakers and it's useful to see that at a glimpse, but for most of the time it's easy to ignore the notification area if you are not interested.
Still at least with the notification area there is some hope as you can set it back to how it was, Except, now that one little icon takes a lot of space and if you make the toolbar 2 units high you can only get 2 icons vertically, so the waste of space isn't especially resolved.
Here's how I fix the Vista/XP ToolBar problems:
I make the taskbar 2 units high. Nice and Simple!
You get a lot more running applications in the taskbar before it gets overly cluttered (to the point that my head gets cluttered before the taskbar).
- You get 2x as many applications in the quick launch toolbar.
- You get 3x as many applications in the notification area.
- You get to see the date, time AND the day of the week in the clock area (which I really like).
On a default Windows Vista/XP set-up anything more than 6 icons in the notification area is a pain and similar for the quick launch area.
With 2 units high I have 18 quick launch apps, 13 notification icons, the date, time and day and currently 11 running applications without a problem.
Now I have a 22 wide-screen monitor so things are a little easier but I run exactly the same set-up at work where I have only a 19 square monitor and it works just as well, if not better as the quick launch and notification area don't take up hardly any room.
So you have two choices:
- Implement a really easy change to Windows 7 and make the toolbar 2 units high by default, keeping everything else exactly as it is in Vista and XP so building on what you know and not introducing new code.
- Change the taskbar to a new way that people have to adapt to, change the way you quick launch applications, change the way you see your notification icons, introduce new and most likely more complex code to the Windows 7 Code base which will not have been tested as well as previous versions.
Personally, I think that the XP/Vista taskbar works well and that making it 2 units high solves the problems with the quick launch and the notification area and making the change in Windows 7 just introduces code that isn't needed and with no doubt lots of new and fun bugs.
Fingers crossed that theirs an option to use the previous taskbar implementation in W7 or failing that some amusing adverts mocking the new taskbar so the pain has some good.
I just uploaded a new version of DinnerTimer.com which moved from being a .net 2.0 site to a .net 3.5 site, the server has .net 3.5 installed and every thing went well until I navigated to DinnerTimer.com
I was greeted by :
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
The error message in the event log was :
Message: Could not load file or assembly 'System.Web, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is denied.
This struck me as a little crazy as all my other sites on the server are .NET 2.0 and the previous site was .NET 2.0.
After much searching on the net and trying a variety of things (including giving permission to the various IIS accounts to .net 3/3.5 folders in windows folder and setting up a dedicated 3.5 App pool for the site) I finally added IIS_WPG permissions on the "Web Sites" folder in IIS manager and the site magically appeared. Now I just have to wonder what the security implications are and if that broke any other sites.
You have to love simple upgrades! I'm not sure if this is a general issue with IIS or because I'm running plesk which uses different security & user settings to a normal IIS setup.