Skip to main content

Vista, HP DV2210us freezes at start of waking from sleep/hibernation

[also see this]

This is a HP dv2210us which has a Go 6150 graphics card. From this microsoft knowledge base entry, assuming that this card has a PCI-E bus (NVIDIA tech specs), I need this hotfix.

The hot fix doesn't work for me.

The computer is now such that it will not boot up easily - it gets stuck at a blank screen whenever I switch it on. I have to coax it to get past what ever is stopping it by hitting f8 and catching it at the right boot phase.

I'm gonna wipe the hibernation file and see if that works. No

I do get an error - \boot\memtest.exe 0xc0000221 file possibly corrupt, header checksum does not match the computed checksum.

I think I will restore the computer to the factory default (yes, I do not have vista disks, thank you HP and Microsoft).

2008.03.18: I think the computer has a problem shutting down when it is asked to restart.

2008.03.22: Apparently the HP service techs know about this problem and will fix it since it is under warranty. They promise delivery on April 15, so I will be laptop free for about 3 weeks at least. That said HPs warranty covers home pickup and delivery, so thats a bit less hassle. Now if only they had a loaner laptop service...

Comments

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty