Two problems with 7264.x64 . . .

[mtp]

this may be the problem

for chipset and AHCI drivers, i'm just using the ones built into win7 for now

Try disabling AHCI or using the vista 9.0.0.1008 drivers installed in Vista compatibilty mode for all users.

Disabling AHCI helped with a number of sleep problems I was having in 7264 x64.

Mark

 

[DJG]

So it's apparently a problem with 7264, which had a warning about a showstopper ... n'est ce pas?

 

[PotatoMan83]

7264 had some problems with me too (removing windows components) so I went back to 7260. I also had noticed my wireless going off and on with the 7264 but not too much. 7260 has been the best build for my system yet. Hope they lean more towards this build in final.

 

[weh]

The sad thing is that -- up until I upgraded from 7232 -- I had been clean-installing on alternating drives; so that, should I encounter problems, I could simply pull the current OS drive and slip the previous OS drive back in its place. Unfortunately, this time I upgraded and migrated the resultant amalgam to my long-intended, 2-drive array, using both of the drives I had been alternating.

Stupid, stupid me! I should have known my action would guarantee I'd have a problem of some sort.

I do still have the much older 74GB Raptor drive on which I'd installed build 7100.x64 -- which is what I'm using at the moment. It truth, there isn't one heck of a lot of difference.

If I do another fresh install before RTM becomes final and leaks -- if it actually does, I am probably going back to 7229 -- the last "official" release in ISO format before the pre-RTM series.

 

[weh]

So it's apparently a problem with 7264, which had a warning about a showstopper ... n'est ce pas?

I remember reading that. Should have paid more attention. We all get caught up in the new build game. It's a blood-thirsty feeding-frenzy every time a new leak is even hinted.

I do have a work-around -- thanks to Antman's suggestion that disable power cutoff of the affected devices in the device manager. I may just go with that.

Having installed and re-installed nearly a dozen different builds, to quote Madeline Kahn:

​

 

[fakeasdf]

So it's apparently a problem with 7264, which had a warning about a showstopper ... n'est ce pas?

Actually 7264 was a build to fix some showstopper bugs. There was a forum post about someone saying there was a showstopper bug with 7264 because his system had halted while copying a file over the network. That was not a confirmed showstopper. That's all the information about 7264 and showstopper bugs. All of this is based off of what I'd read from Wzor... so I could be wrong, but Wzor generally has pretty good information...

 

[DJG]

Actually 7264 was a build to fix some showstopper bugs.
...

There was a forum post about someone saying there was a showstopper bug with 7264 because his system had halted while copying a file over the network....

That would've been moi ... but yeah, as I mentioned back then, who knows what the refered to "showstopper" was / were.

I remember reading that. Should have paid more attention. We all get caught up in the new build game. It's a blood-thirsty feeding-frenzy every time a new leak is even hinted.

I do have a work-around -- thanks to Antman's suggestion that disable power cutoff of the affected devices in the device manager. I may just go with that.

Having installed and re-installed nearly a dozen different builds, to quote Madeline Kahn:

Ahh, good ol' Mel Brooks classic . I upgraded a lot more than clean-installed, only for 7100 & current 7232. I do an image backup before upgrading / clean installing, so I can quickly revert to my previous version - takes me about 6 minutes including booting from the recovery CD, 9 minutes if you add the backup time. OK, I do have an obscene amount of disk space ... sue me.

But dang, I haven't had a leak fix in almost a week now, I'm going cold turkey ...

 

[Chappy]

Remember also, these builds are NOT meant for public use or use on a main machine.
Interim builds with fixes for found issues often break many small things as a result, and many times the Sleep or Hibernate features respond to something that's now not functioning properly.
These are very sensitive features and often don't respond well even in a more or less stable environment, and I would say that if it worked well with other builds but now doesn't, this may be the reason. Of course one way to know is to install an older build that you know didn't have this behavior before, and see if it works Ok there or is still broken.

 

[DJG]

Remember also, these builds are NOT meant for public use or use on a main machine.
Interim builds with fixes for found issues often break many small things as a result, and many times the Sleep or Hibernate features respond to something that's now not functioning properly.
These are very sensitive features and often don't respond well even in a more or less stable environment, and I would say that if it worked well with other builds but now doesn't, this may be the reason. Of course one way to know is to install an older build that you know didn't have this behavior before, and see if it works Ok there or is still broken.

Damn, and all this time I thought "Beta" was just misspelled "Better"! :shock:

 

[heslo]

I seem to have a problem with shutting the machine down. It just hangs there for a few minutes with the "Shutting Down" message then turns off. Clean install too :/