Discussion on:
View:
Show:
I tried running it on my Toughbook CF-29, but had a tendancy to lock up hard (power off/on). I have a dual core x64 system, just hadn't had a chance to load it up on that.
We have it running on an ASUS EEE slate. We had to delete and redetect the wireless adapter to get it to connect to our wireless networks, but after that it seems to work great.
Have to do a regeristery tweek to get what should be an option.
And if they screw up the O/S then MS will say your problem should NOT be there.
Na not for us WIN8
And if they screw up the O/S then MS will say your problem should NOT be there.
Na not for us WIN8
Why play with alpha or beta stage software if you plan on looking at it as if it were a finished product?
Because that is exactly the best time to let MS know what you like or don't like. What are you trying to say? Wait until it's finished then gripe?
Not Public Beta, not final (or even close to final) Release Candidate, and certainly not Final Product. It's being put out primarily so developers can adjust to and work with it and see what may need adjusting for their products. The wider release is just gravy for those of us who have to (or like) playing with early releases to get a feel for what's coming.
If it's like this in the final version (which I would find rather... short sighted of Microsoft to not have the option somewhere "official,") then you'd have a point.
If it's like this in the final version (which I would find rather... short sighted of Microsoft to not have the option somewhere "official,") then you'd have a point.
... would be to try to encourage early developers to find interesting ways to make use of the new interface. If all of the early developers immediately turn it off with a one-click setting and work on their apps in that environment, of course it's going to be terrible once released.
A user option would be discoverable via the UI either during or after installation. A Tweak is just a hack that is not for the common user. Of course, these definitions don't necessarily apply to pre-release versions.
I like both start menu's in their place. Can you get it so that when you call the desktop from Metro the start button works as it did?
It would be good to have the option for both. I do like the Start Menu as it was, and if possible also a link back to the Metro. What is the process that starts the Metro, cause then maybe it could be placed as a Start Menu Item?
All in all I must just say that I am really impressed with Win 8 and can't wait for this to finally be released
All in all I must just say that I am really impressed with Win 8 and can't wait for this to finally be released
Just had a play and found pressing the Windows key twice will switch between Metro and the desktop. I also notice that it removed the ribbon. Whether that is good or bad is up to personal preference.
I think this will be great for touch Tablets with the Metro tiles, but I don't see that purpose useful for non-touch devices. However, I like the tweak as I love the interface of Windows7.
But there is one problem, how do we get the look of the Start button from Windows7 on Windows8?? I find the new button on Win8 a bit plain as oppose to a nice fresh look of Windows7 button. That would be a great tweak!!!
But there is one problem, how do we get the look of the Start button from Windows7 on Windows8?? I find the new button on Win8 a bit plain as oppose to a nice fresh look of Windows7 button. That would be a great tweak!!!
I wouldn't worry, the final version will either give the option of classic view with everything looking like Window 7 but with the new ribbon in explorer or it could also check the system hardware during setup and if it doesn't find any touch capable device actually installs the old desktop environment. As this prerelease is for a targeted audience I wouldn't start fretting until it gets to Beta 2 stage.
I thought "classic" was the standard interface of w2k or the classic option in win xp.
But maybe something that is two-three years old should now be considered classic
The only thing that seems to be consistent in pc-interfaces is constant change...
But maybe something that is two-three years old should now be considered classic
The only thing that seems to be consistent in pc-interfaces is constant change...
Yes, I have downloaded the Windows 8 Developers Preview, and installed it, as well.
I used Oracle's VirtualBox (www.virtualbox.org) to run it in a VM.
My first impression during installation was being offended at the push to link it to my MS account... the very last choice was the option to create a standard user name.
During installation, I noticed the crude 'slide switches'... and then realized that this new UI for an old bloated code base, was indeed, rushed out, so that MSFT may grab as much of the tablet and smart phone business as possible.
How hard could it be, MSFT? To finally get off your a$$ and have a sound back-end which would be interfaced by numerous skins?
Users dont care about the code, other than it works dependably and efficiently.
What they care about is the interface.
These are my suggestions:
1) Fix the bloated code base that Windows has become. i.e., quit adding to it and build a robust platform.
2) Design UI's that everyone can use. i.e., use 'skins' that can make users comfortable with change (because it still looks familiar and they don't have to learn a new way to do things.)
Take the 'Ribbon" interface that was forced down the business worlds throat, beginning with Office 2007. It has cost the companies that use(d) Office, quite a bit of money in lost productivity and retraining. This could all have been avoided by letting users choose the UI they wanted... "Click here to use Office 2003 interface".
When they came out with Win7, most people thought it was too soon. Now Win8 is coming in so fast, it smells like greed. I already know the majority of the business world is pretty tired of the 'push tactics' used by MSFT. They (MSFT) are falling over themselves to get the latest 'new' thing out to the masses.
Remember when we had a new model (major change) in automobiles about every four years? Well that didn't make them as much money, so now we have a new model every year!
Thinking about buying a cell phone? Hesitant to sign up for a two-year contract,
when you know that your phone will be outdated (or will be made to feel that it is) by next week?
Well don't worry, that hesitant feeling is your common sense, letting you know something is wrong.
As an aside, this is a post to my Facebook friends, who had an e-fit, after yesterdays latest UI change.
(Which, by the way, we will probably see even more (changes), because of the Google+ rollout.)
"The main thing to remember is to bitch to the correct people. Bitching to your friends or the world at large isn't helping matters. Bitch to the developers... they are the ones who are making the changes, not your friends.
The world changes so quickly these days, and if you ARE pouring 100% of your energy into changing it for the good (probably with he use of a computer and its respective UI's), having to accept change in your primary tool, so often, just brings more frustration.
Can you imagine a carpenter, who is trying to build a house, having to change the way he interfaces with his hammer or saw, every week or so?
He would most likely give up, because true productivity comes from being familiar with the interface to the point it becomes second nature."
Same goes for MSFT.
I used Oracle's VirtualBox (www.virtualbox.org) to run it in a VM.
My first impression during installation was being offended at the push to link it to my MS account... the very last choice was the option to create a standard user name.
During installation, I noticed the crude 'slide switches'... and then realized that this new UI for an old bloated code base, was indeed, rushed out, so that MSFT may grab as much of the tablet and smart phone business as possible.
How hard could it be, MSFT? To finally get off your a$$ and have a sound back-end which would be interfaced by numerous skins?
Users dont care about the code, other than it works dependably and efficiently.
What they care about is the interface.
These are my suggestions:
1) Fix the bloated code base that Windows has become. i.e., quit adding to it and build a robust platform.
2) Design UI's that everyone can use. i.e., use 'skins' that can make users comfortable with change (because it still looks familiar and they don't have to learn a new way to do things.)
Take the 'Ribbon" interface that was forced down the business worlds throat, beginning with Office 2007. It has cost the companies that use(d) Office, quite a bit of money in lost productivity and retraining. This could all have been avoided by letting users choose the UI they wanted... "Click here to use Office 2003 interface".
When they came out with Win7, most people thought it was too soon. Now Win8 is coming in so fast, it smells like greed. I already know the majority of the business world is pretty tired of the 'push tactics' used by MSFT. They (MSFT) are falling over themselves to get the latest 'new' thing out to the masses.
Remember when we had a new model (major change) in automobiles about every four years? Well that didn't make them as much money, so now we have a new model every year!
Thinking about buying a cell phone? Hesitant to sign up for a two-year contract,
when you know that your phone will be outdated (or will be made to feel that it is) by next week?
Well don't worry, that hesitant feeling is your common sense, letting you know something is wrong.
As an aside, this is a post to my Facebook friends, who had an e-fit, after yesterdays latest UI change.
(Which, by the way, we will probably see even more (changes), because of the Google+ rollout.)
"The main thing to remember is to bitch to the correct people. Bitching to your friends or the world at large isn't helping matters. Bitch to the developers... they are the ones who are making the changes, not your friends.
The world changes so quickly these days, and if you ARE pouring 100% of your energy into changing it for the good (probably with he use of a computer and its respective UI's), having to accept change in your primary tool, so often, just brings more frustration.
Can you imagine a carpenter, who is trying to build a house, having to change the way he interfaces with his hammer or saw, every week or so?
He would most likely give up, because true productivity comes from being familiar with the interface to the point it becomes second nature."
Same goes for MSFT.
The keyword is preview - this is not even a beta version of Windows 8. But even with that said, I find Windows 8 to be anything but bloated. It boots from power on to login screen in 11 seconds on my lowly Dell Studio Hybrid test PC.
Perhaps it is your VM that makes Windows 8 seem bloated.
Perhaps it is your VM that makes Windows 8 seem bloated.
I see I have a negative vote already...
Does the caster want to offer better insight or an explanation for refuting my opinion?
Does the caster want to offer better insight or an explanation for refuting my opinion?
Seemed to run fine under Hypervisor 1 core 768Mb RAM. Installed size about 12Gb.
Funny thing I discovered when installing at home; Windows 7 Virtual Pc is limited to 32bit guests. I loaded it under Virtualbox instead, to have the developer tools.
Overall I'd have to call the Metro interface a new Start Menu, not a new interface.
Our web application depends on a 32bit ActiveX viewer, which ran fine under the 32 bit IE (not the default), as it does on Vista and Win7 64 bit OSes. I was able to add a shortcut to the Metro Start Menu, but after closing IE, it returns to the desktop, rather than the Metro. I suspect that behavior will change closer to release, and may end up being selectable (for the manufacturer any).
FYI - Hypervisor is an option in Windows Features. Since I am running under Hypervisor, the core option was disabled.
Funny thing I discovered when installing at home; Windows 7 Virtual Pc is limited to 32bit guests. I loaded it under Virtualbox instead, to have the developer tools.
Overall I'd have to call the Metro interface a new Start Menu, not a new interface.
Our web application depends on a 32bit ActiveX viewer, which ran fine under the 32 bit IE (not the default), as it does on Vista and Win7 64 bit OSes. I was able to add a shortcut to the Metro Start Menu, but after closing IE, it returns to the desktop, rather than the Metro. I suspect that behavior will change closer to release, and may end up being selectable (for the manufacturer any).
FYI - Hypervisor is an option in Windows Features. Since I am running under Hypervisor, the core option was disabled.
If you add quicklaunch to windows 8 as well as turn off metro, the start menu button turns into the round icon from windows 7
By the way, how do you add quicklaunch to windows 8 as well as turn off metro? I'm going through the options but can't seem to find it.
Thanks!
Thanks!
- Keyboard Shortcuts:
- Prev
- Next
- Toggle

































