Recently, while making some changes to the Attunity RMS CDC code, I experienced a system crash when testing the edits on Itanium. The Attunity RMS CDC code, as much as is conceivably possible, is common source code for all of the supported OpenVMS architectural variants; thus, I was rather puzzled that these new edits would cause a bugcheck and crash on Itanium, but not on Alpha. Perusing the crash dump, it turned out that the bugcheck was precipitated by a ROPRAND fault on the Itanium's equivalent of the VAX INSQTI instruction. In the system dump analyzer, I examined the address in Itanium register R32 which should be the queue header. Verified! It was properly quadword aligned. I then examined the address in Itanium register R33 which should be the entry address. It too was quadword aligned. Why then should it be evoking a ROPRAND fault? (read all 2228 words.)
My envy is not my ENVY17
My venerable old 17" Toshiba Satellite has been demonstrating that its time is nigh, so I'd been shopping for a new laptop to replace it. The selection criteria was simple — 17" display, keyboard with alternate/numeric keypad, and it had to be capable of fitting comfortably into my red Vanguard® attaché case along with my 17" MacBook Pro. I looked at several candidates and had narrowed it down to two; another Toshiba or an HP Envy. The Envy was thinner but also much pricier; however, I was able to get a nice discount which brought the HP Envy in at about US$1000.00 including the state sales tax. So, I made its purchase. This is the first system that I have purchased new with the added baggage of Billy-tax — Micro$oft WEENDOZE. Hear it not, Duncan, for this system never booted this demonic seed! It was erased from the drive upon arrival and I began my protracted sojourn to install Ubuntu. (read all 2249 words.)
Frontpage
