Pre-Beta/Beta testing and evaluation is best performed in daily usage live scenarios (if able) RRS feed

  • General discussion

  • Some people think I'm nuts, but the main "production" client I use everyday has the developer preview edition on it....  Pre-Beta/Beta testing and evaluation is best performed in daily usage live scenarios (if able).  I have used the client on a daily basis since day one of its release to appropriate MS Partners....  love it and other than a few "scratch the head for a few secs" issues... have enjoyed using it daily.

    How else does someone fully and better evaluate and test an OS platform, software, hardware, etc?    You put it into normal daily usage and then when issues arise, be a good IT consultant and exercise proper problem resolution skills and go about the rest of your day....  If you planned the install right, then recovery from critical or fatal issues should be a SNAP.   .... Otherwise, you never "really" know what it is like in real life.  Do you buy a car before opening the door, sitting in it, turning the engine over, driving it around on REAL roads, then getting back out looking it all over...  maybe even sit in the back seat and all?  Of course not, neither should anyone do the same for the main operative nexus for their everyday computing.... 

    I love (for the better and most part) the direction and the progress Microsoft has made with this next-gen OS release. Can't wait for a future Beta release to test and then onward to the future with RTM and the Retail.

    Just one guy's outlook on things, I know, but there it is.  What is your take on the beta in live use question?

    Sunday, October 23, 2011 3:15 PM

All replies

  • the main "production" client I use everyday has the developer preview edition on it.... 

    How else does someone fully and better evaluate and test an OS platform, software, hardware, etc?   

    Install the pre-release software on a secondary computer and test it how ever you like while keeping the main computer unchanged in case something happens to the test/beta software.



    You should not install Windows 8 Developer Preview on your main computer - it's not even a beta product yet and bugs are to be expected.
    From the main download page:
    The Windows Developer Preview is a pre-beta version of Windows 8 for developers. These downloads include prerelease software that may change without notice. The software is provided as is, and you bear the risk of using it. It may not be stable, operate correctly or work the way the final version of the software will. It should not be used in a production environment.

    Also, it is stated on the Windows Developer Preview download page that you must reinstall the previous OS:
    Notes about installing the Windows Developer Preview
    You can't uninstall the Windows Developer Preview. To reinstall your previous operating system, you must have restore or installation media.

    Sunday, October 23, 2011 5:17 PM
  • While I definitely agree that my method is not for the faint at heart, nor non-IT person in general; I do believe having a "secondary computer" for testing does not fully match nor meet day-to-day usage scenarios.  Thus, my personalized philosophy noted initially herein.  Otherwise, I agree with everything you said.
    Sunday, October 23, 2011 6:19 PM
  • While good note for general public, the web-text blurbs you posted were well known by this author well prior to them being even posted.  Have tested Microsoft applications for many years and my tried and true experience has brought me to where I am today.  Those same experiences are what have given me an overwhelming edge over the atypical IT consultant in my area.  Hint, hint.... 
    Sunday, October 23, 2011 6:22 PM
  • Paul, it sounds like you went into this with yours eyes open and a back out plan if it all went pear shaped, you're a braver man than I but good luck to you :)
    Acer W500 tablet & dock, New 'works' Lenovo laptop Too much apple stuff. Remember: A Developer Preview is just that, a preview for developers - not everything will work 'just right' on day 1.
    Sunday, October 23, 2011 6:30 PM
  • "New 'works' Lenovo laptop"  I like that.... Lenovo makes great pcs and laptops.  Wonder why they don't advertise more, though.

    Thanks for the wishes!  ;)

    Sunday, October 23, 2011 6:35 PM
  • as long as a working backup exists i don't see why anyone would get excited or have a problem with someone testing this preview to the fullest extent. maybe you should beg their forgiveness? i agree with your statements paul. good luck to you!
    Sunday, October 23, 2011 6:44 PM
  • I had a couple problems with files saving in the developer preview. One causes all programs to crash when accessing WinInet cache. The good thing is that the code in WInInet asserts and breaks into the debugger instead of hiding the problem like Windows 7 PCA and corrupting data, but you can't count on programmers to write enough asset statements.

    Don't put too much trust on the data you use the developer preview to access (e.g. files you allowed Windows Defender to scan or contacts you allowed to sync to your hotmail). Make sure you always have backups.

    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Sunday, October 23, 2011 7:45 PM
  • Have not had many issues at all so far.  Been a bit since BUILD, too.  There have been a few apps that needed compatibility options to install and run right, but overall.... doing well.  I still, though, find the new Start menu a bit clunky....  There should be an option to revert to Win7 style Start menu, in my opinion... and if there is... I have not found it yet.  I find it very snappy though even on older desktops and laptops... definitely recommend 2GB or more RAM....  it'll install and run with 1GB, but will not perform well.  I also find the 32bit edition best especially in the case of older printers and other hardware.  For all the people out there crying about audio not working etc... BING the win7 or vista drivers for the audio chipset... use them....  I have had NO problems with a multitude of systems of wide variance in hardware.... sometimes it takes a while to find the right drivers... but HEY, hello.... this is a pre-beta release and not at all for the faint (or non-IT) at heart.  Instead of crying.... wait for a more mature beta release or better yet release candidate if you are not adept at troubleshooting computers.

    Bravo, though, Microsoft!  I can't wait for the refined releases due out later on.  ;)

    Tuesday, November 22, 2011 5:37 AM
  • One doesn't have to uninstall their previous OS to install the Windows Developer Preview. All one needs to do is create a primary partition (min 20GB for 32 bit, 30GB for 64 bit), with their currently installed OS. Win 7 has it's own partition tool, there's plenty of others also. That is, if one has plenty of drive space. Many modern PC's & notebooks ships with drives of at least 320GB, it's more common today to have a 500GB as stock.

    However, to do this with Win 7, one will need to backup their recovery partition & delete it (or change it to a logical partition), to have a data partition, only 3 primary partition are allowed. With XP, this may or may not be an issue. But those users don't have the 100MB partition to be concerned about.

    Here's the instructions. This works with either XP, Vista or Win 7, as a dual boot.


    Actually, though Win 7 Pro x64 is my main (OEM) install, I'm dual booting XP Pro x64 & Windows Developer Preview on a separate HDD. If Windows offers special upgrade pricing like they did with Win 7 (about 3 or 4 months before release), I may consider upgrading my desktop.

    If there's any confusion as to how to access these options from Windows Developer Preview, it's as follows:

    Control Panel > System and Security > System. On that page, on the left, are 4 options. Choose "Advanced System Settings", then "Advanced", then "Startup & Recovery", & you'll be able to choose the default OS at startup.  I chose "Earlier Version of Windows" (like it shows in Win 7) as default. It (XP) won't show up otherwise.

    And remember, before doing anything, as always, backup what you have. That way, you retain the original bootloader.

    Hope that my post is useful.


    Tuesday, November 29, 2011 7:26 PM
  • Who said anything about:  "uninstall their previous OS to install the Windows Developer Preview."  This thread was about pre-beta and beta testing on live ("production") machines being the best manner of doing so.... you can NOT do that in dual boot.....  do you flip flop OS's all day long doing the same thing in each OS version in the course and scope of daily operations?  No, not many people would either....  thus, as this thread states (opinion, of course), that doing any REAL testing requires blind faith usage of the OS (or other app being tested)....  if you encounter issues... you DEAL with them... just like you DEAL with issues on Windows 7 (like trying to find Vista drivers for an old printer or something....)  the only difference is the OS, not how to deal with issues in any OS...

    Anyways, I respect what you said and are trying to get across, but ....  that reply is best suited for another thread (See http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/152d7895-4281-427d-a6e1-40af0d8648ec  ).

    Tuesday, November 29, 2011 7:47 PM
  • Still all these months later and I am still a happy (in production) user and network admin.  I use nothing but Windows 8 Develor Preview client & server in house.  Despite a few quirks that are tolerable, I love it and my users love it.
    Wednesday, January 25, 2012 2:55 AM