I tried that now (on F9) but same result. This is what I get after resume from standby, But even on the times the "SLIC" table stayed, the activation "disappeared". I'll try your file and report back.
There is another method (SSV1). But at this is reported sometimes a sleepstate issue as well. (At other Gigabyte bioses). So the ISA method was the method No. one so far. I assume ISA3 (only) is the same as well?
The easiest way is to stick with that issue. But I can try for a SSV1 mod, but this means another "risk" to flash the mod, because that bios contains sensible modules. I can do it tomorrow. Just tell me if you want it to try. There is a little chance to fix that issue. Yen
The Mobo has a DualBios so hopefully it can take it. If you have the time - I would appreciate it. I noticed ver F9 causes the CPU fan to go faster and make a little more noise, so F8 should be first priority. Thanks P.S I've been using the onboard "QFlash" utility, is it better/safer booting into DOS and using the "FLASH895" program?
This just came in my mind that maybe the sleepstate issue wouldn't be at the F9 version....... Anyway, O.K. tomorrow I'll try it. To flash from dos is IMO the safest way. But the onboard utility is fine as well. Only winflasher I wouldn't prefer. Yen
You should try the original bios and check for this issue, before I'm trying a new mod, of course! I'm waiting for result. To mod it before makes no sense. Yen
I'm not sure which issue you're referring to. The original bios from Gigabyte (obviously) doesn't activate vista and I don't have any problem waking the computer from an s3 sleep state with either the original or modified bios (ver. F8). The problem seems to be that the bios "changes" when coming out of sleep and the SLIC becomes unidentifiable. Edit: I've noticed that when using Fzeven's mod (F8), Everest still shows the SLIC table when returning from sleep, but activation still fails.
I'm having the same problem on my GA-P35-DS4 Rev 2.0 using the softmod. It was working fine coming out of S3 sleep mode until I installed the latest version of SP1. On a reboot it is re-activated. Hopefully someone will find a solution.