Long delay when quitting back to main menu

[frankmcg]

Same with me I'm afraid, same error and same behaviour.

[SoupSatchel]

Have this message (which may be the same as the other dialog but it might help) when the machine wakes up (having applied the wake up patch to solve my going to sleep problem!)[ATTACHMENT NOT FOUND].

I can't continue into GBPVR this time either, I have to quit, continue just produces the same message.

Hope this helps, as always you seem to have a lot on your plate, any help is much appreciated.

[sub]

Ok, lets have one more go at this problem. Please try the attached and let me know.

EDIT: patched removed. See later patch below.

[frankmcg]

Just tried the latest patch out sub. Getting slightly different behaviour this time.

I'm not getting the "object not set" error on first startup any more (which I think you said was resulting from version incompatibility), but after going into hibernate and then waking the machine up again I get a similar dialog box to before. Clicking continue a couple of times on this brings up a white screen with a thin red cross running from corner to corner! I then have to close GB-PVR using my remote shortcut key.

V strange but thanks for all your continued efforts on this, especially as it doesn't seem like it's affecting too many people.

[sub]

I'm not getting the "object not set" error on first startup any more (which I think you said was resulting from version incompatibility), but after going into hibernate and then waking the machine up again I get a similar dialog box to before. Clicking continue a couple of times on this brings up a white screen with a thin red cross running from corner to corner! I then have to close GB-PVR using my remote shortcut key.

Can you reproduce this then post the logs?

[SoupSatchel]

Similar behaviour here, initial start up smooth, resume has error box as before, continue just loops back to the same dialog, have to quit and reload GBPVR, dialog box gives [ATTACHMENT NOT FOUND], logs [ATTACHMENT NOT FOUND]

[frankmcg]

Any more thoughts on this one sub? Although strange it isn't affecting many people - I would have thought the majority of users are using VMR custom (or FSE) and using some form of hibernate/standby?

[sub]

Sorry for a slow response. Here is another go at it.

It'll probably take about seconds after resuming to reacquire the device. You shouldnt need to, but if you find it resumes to a black screen then try pressing a key.

[frankmcg]

Still not working for me I'm afraid. After coming out of hibernate I'm just getting the same dialogue box as before with a white screen and a thin red cross through it. This time around I also needed to do a hard reset as well as it wouldn't let me click on the dialogue box to kill it.

[sub]

Thats odd, I applied that patch to both of my v0.99.12 "production" boxes yesterday, and it seems to have fixed the problem on them. I tested it numerous times yesterday and it work fine every time.

Can you post you logs with the lastest patch applied?