Ok I hope I will not be shoot in pieces, for that post here, but I hit something strange in Windows 7 beta 1, I searched on this particular issue on connect, or on the net but did not find similar problem... I know that it does not belongs here, but I am writing some apps which are heavily using win api (like saving openning writing to dbase tables etc..) and the best way to test an OS is to used this way, so I hit these problems when writting the apps.. This is part one of the problem (with workaround).. So the problem is this when I put my laptot, which is acer aspire 1650wlmi, with intel 915 Express Mobile chipset, into sleep and then I wake it up, the wireless adapater (Intel BroadCom BG 2200) wont connect to my wifi router, the wiffi connection wizard does not see any networks (which are 100% around me), but when I disable the device and enabled in device manager, again all wireless routers are visible and windows connects to my router automaticaly. Funny is once the device manager closes or sometimes not so here is the part two of my problem... Part two is uglier When the computer awakes, everything seems to be fine, no BSOD nothing..., but then when I begin working with applications which were running, they begin to behave very strangly, like when you call a OpenFile Dialog, it appeers, but you cannot change to another folder, nor change the drive, or when the OpenFile/SaveFile dialog opens on the root , you see the drive icons but not drive space information (e.g. you see documents, downloads but no the icons which are normaly positioned on the left or the right side of the label), again you cannot change to the particular drive... This most evident when calling a winApi function or some win system call, if the applications is calling it own methods there is no trouble But the when you want to quit the application it wont quit, you cannot kill the app neither from task manager or process explorer, the application is running, with all running threads, which also cannot be killed... to discover this I let run the process explorer through the standby/awake scenario, becuase I can not start it once the system awakes... Some applications can be run, I wanted to use the snipping tool but it run I could select the area, but then again SaveDialog was not able to change location or save the file.... When starting application some start normaly, but with the above mentioned scenario, like the snipping tool, or calculator, e.g. iTunes starts, but the applications is not visible, again visible in task manager or process manager with no possibility to kill it... I tried to log off and log in, but the apps are there running like detached from the api calls, but with allocated memory.. This is particulary in Visual Studio Express, tried it also with Delphi 2009, Eclipse all have the some problem, Flash CS3 is also affected... Restarting the system is also not possible you get to then Windows is shutting down, only hard shutdown is possible (powering off). Hibernating the laptop will not lead not to this caveat.. I am sorry for this here I send a feedback, but did anybody found this strange behaviour in Windows 7 beta1? Or is this connect to my configuration. It is really annoying becuase when I forget and standby/wake up I cannot continue Again I am sorry that I misuse this forum but I had to ask? Sorry for the english, no english man..

My computer is doing similar using Windows 7 x64. When I come back from being away for awhile it seems various apps are frozen. Yet I cannot close them, and I am unable to get to task manager to end the task. I also cannot log off or restart. Nothing works except hard reset. I have even let it sit overnight with frozen apps hoping they would resume function but to no avail.This has also happened when not resuming from a lower power mode where an app freezes and I am unable to do anything but a hard reset :(It is odd behavior though since I can click certain things as if it's not frozen.I also have the wifi issue and I am using an actual linksys wireless n driver, it was so difficult to connect that I rearranged my house so that I could be plugged directly into the router with ethernet.

Thanks much for the reply...I begun to think it is about the my particular wiffi driver and machine, but I see I was wrong. The problem is that, that I cannot send and real debug information, becuase whenever I try run any app like process explorer or debuger, the application starts and hangs, but I think there somewhere in the network stack of wireless part is something fishy, I will try to deactivate my wirelless and make the stanby/wake scenario.. I will post the result.....

same issue(s) here with the 32 bit OS. When waking (or attempting to) from sleep, the platform is frozen. Only recourse seems to be a hard reset.

same here (i got a 32)it freezes almost everything when it "wakes up"it seems to work fine if the CPU has something to do though. if i am downloading, burning a disc, or BOINC'ing, then it wakes up fine

I have the 32 bit version of the beta and I have not found one problem with it. I actually have not noticed the freezing or lock when the OS wakes up. However, I did notice that it doesn't take long to go to sleep but that was simple to adjust. So, I guess my overall opinion would be that it runs similar to that of an NT machine with a modified vista look. Although it is 10 times smoother than vista even vista sp1. So far so good MS gets a thumbs up. We will see how the coming weeks of abuse brings to the table.

do you have the latest chipset driver? i would try that first

I tested it with Intel Chipset drivers - Mobile Intel(R) 915GM/PM/GMS/910GML Express Processor to DRAM Controller - 2590, these drivers are from Microsoft from 21.6.2006, 6.1.7000 (probably same as the windows 7 build),I think this is not a driver issue, i think that explorer itself is affected, but when you kill it and run it form task manager it starts, but shortly hangs... Funny though is there is noBSOD.. I seems to me like the function calls are detached form the API whithout the OS is knowing about it( :) mu thought dont kill me for it...)I uninstalled the Wireless adapter from device manager, restarted the system andcanceld the driver instalation, performed thestand by/wake up scenario with the same result as I mentioned above.Confirming thethis is probably somwhere in theAPI of theos, becuase like Win32APIfunctions for open/save file dialog, are affectedis the same for Vista dialogs., what ever wants toaccess the directory/file structure hangs and cannot be killed. I confirm that this is the same when you try write or open a file directly from your program (without openfile dialog) I can send the code, just simple loadFromFile function....Sumarized, application which want to acces the directory, disk, filestructure hangs no matter what you do, you cannot change folder, nor location, everyone who knows win32api openfile dialog, when you press the combobox for directory structure the app hangs... this is same for Vista API OPendialog..I did not found any workaround I have Windows 7 beta 1 32bit English Version...P.S. I really cannot send any data, when I try to acces the running process, what service is hanging the app stops to respond, If anybody (from the dev team could look at it it would be nice, I am ready to help, but I cannot get any info from the OS after wakeing it up...)

OK Confirming I was wrong resuming windows7 after hibernation leads to the same caveat as wakeing up from the stand by.... This is very annoying , although the overall respinsiviness of the OS is marveolous, starting shutting down, app launching, visuals are stunning just this little bugling :)...

I too have problems after standby (S3) with Windows 7 x64 Beta 1, there is no video output and I can't even login remotely (ping doesn't work either!).Only a reset or a forced shutdown works.(I've seen similar problems with Windows Vista x64 SP1 too, when resuming from standby the login screen is frozen, but video output works).

Hi all,I have no problems like you describe in previous posts but i did have it in vista my mouse would be frozen and according to some experts with the same type of machines (Dell xps 630i) it is caused by the nvidia driversClaude

I have a saphire (ATI) card for video and intel chipset for mobo so nvidia drivers couldn't be the issue.I have yet to figure out how to fix this, I keep turning off certain power mgmt functions and it still happens when I haven't been around my computer for awhile. I would just like to know if anybody at microsoft has any idea what is causing this and if a patch will come out. I mean are patches coming out on windows update for the beta, or do we all just have to wait until another beta to see things fixed?

OK so I have been looking and looking... this think is funy, there is no trace of a problem in event log, in perfomance monitor, what's ever. I think I know for sure that some service/process is bad. I tried this http://www.neowin.net/news/main/09/01/19/windows-7-beta-testers-find-critical-windows-installer-bugit appears there is no conection between this problems, but there is the hanging explorer and problem in services... A have deactivated the windows customer improvement..... service, and resume after standby or hibernate worked, but only to some degree you cannot open a file from within the application you have to open explorer(windows key +e)a click open with a then it works like charn... When you try to open it from the app the opendialog freezes...

OK for all those who have Windows 7 beta 1 and are using Slysoft Virtual Clone Driveherehttp://forum.slysoft.com/showthread.php?t=25373&page=2is a discussion with dev team about it, exact the same problem as I started this threadhere is link tohttp://forum.slysoft.com/showthread.php?t=25660to a beta which should solve the problem with resumeand also uninstalling the older driver is a issue so there is a how tofor me I wil test this this evening, so when this will resolve the trouble I think I will put this thread solved, if anybody tests it sooner feel free to post your resultFunny though MS knows about this problem, but there is no absolutly no mentioning about it, is all about miniportSCSI...

OK confirming uninstalling SlySoft Virtual Clone Drive there is no problem with file acces anymore, Windows is alive a working fine :) I will set this to solved... So everyone who has problems after resuming windows and has Virtual Clone drive installed uninstall it (best way in safe mode) or overinstall it with the latest beta link provided in my forlast comment ....

I have Win 7 32 and a similar thing happens. When I try to turn on the system after sleeping it I just get a screen with my back ground picture and my gadgets. Nothing else. I can change the gadgets, but that is the only thing that works except for alt-tab (which shows no programs). right click doesnt work or control-alt-del or the task bar (its gone).A few other times this same thing happened to me when i was searching for some files except that the 'my computer' screen was open and frozen and when i clicked the X it asked to end the process but it never ended. Another time when trying to 'wake it up' I just got a black screen, mouse and keyboard didnt have power either.

Has anyone found a viable solution to the problem? I am having the exact same problems as the poster above me with the latest windows 7 build.

SkillsToShow said:I am having the exact same problems as the poster above me with the latest windows 7 build. Which is the "latest Windows 7 build"? And is it 32-bit or 64-bit? What's your hardware? Is SATA enabled?Are you using Virtual Clone Drive, as the original poster was?Does the problem occur as soon as you install Windows 7 and its updates, before you install any other software or devices?Just as a point of comparison, I was having similar wakeup problems when I enabled SATA in my BIOS (and then clean-reinstalled Windows 7 beta x64). But when I install Windows 7 with SATA disabled, entering and leaving standby mode works very well.GA-P35-DS3Lr2(F8) Q9450 OCZ8500(4GB) GTX260(WDM1.1/181.71) 2xGreenPowerSATA(1TB)WinTV1600 GGW-H20L 3007WFP Win6.1.7000x64 Avast4.8.1335

Hi I have the same problem when it goes to sleep I get a BSOD with this message:IRQ_NOT_LESS_OR_EQUALhowever I played around with the BIOS, it seems that the crash is consitent with having it on S3 sleep mode ( Sleep 3 seconds ) however when I change it to S1 the problem seems to go away, at least when I had it on S3 I could reproduce it 100% of the times, on S3 so far I have not been able to reproduce it as steadly, so that might be a parcial fix for Beta until the RC comes out.Roberto.