| Blog |
|
| Releases |
| Html Editor | |
|---|---|
|
Date: 16/3/2006 | Work continues slowly on the HTML editor built on top of the HTML viewer control that ships with Scribe. It now has a toolbar:
Recent changes are:
Sure it's no InnovaStudio but I own all the code and it's cross platform and small. So there. |
| (4) Comments | Add Comment | |
| GnuPG Security Flaw | |
|---|---|
|
Date: 10/3/2006 | For those of you that use the gpg plugin for Scribe, there is a security flaw in GnuPG, so if you use gpg you should update your install to the current version immediately. |
| (0) Comments | Add Comment | |
| Windows Is Fun | |
|---|---|
|
Date: 9/3/2006 | Yesterday my PC started the same old trick of ignoring the pre-set video resolution/refresh that I had asked for and set it to some seemingly random res... well seemingly random until I worked out what machine uses that res. My Res util reported that windows was running in 1440x900x32bit @ 75hz. Which is of course what this machine runs at... not the 1280x1024x32bit @ 75hz that MY machine SHOULD be running at (what IS that, operating system envy?). Like I can understand XP choosing a refresh mode out of thin air, but changing to frigging resolution on me? Damn thats low. Of course the LCD just thumbed it's nose at the whole thing and I had to hard power cycle XP to get something running again.
Update: I'm having some luck with a util called Reforce to force refresh rates to what I want regardless of whether the monitor is plugged in or not. *fingers crossed* |
| (0) Comments | Add Comment | |
| Tshirt Idea: I Hate Java In A New And Special Way | |
|---|---|
|
Date: 5/3/2006 | Java sucks, and now you know why. However I don't agree that C++ is worse. At least with C++ you have some damn accountability. If it's broken that the app should be fixed. Whereas with frickin Java if it's broken then it might just be the Java implementation.
Currently all my Java apps are busted because of a bug in the JRE whereby it screws up the local timezone, meaning Java reports the current timezone as GMT (+0) instead of the setting in Windows: Australian EST (+11 currently). I never liked Java to start with. But this just puts the last nail in the coffin, RIP Java. So I need a DVB recording server (ala Webscheduler) that ISN'T written in Java real quick, ideas? Update: Seems Java has a bug that screws up the timezone when automatically adjust for daylight savings is switched on. Thus the easy workaround is to switch it off and manually adjust the timezone to some neighbouring country with the right offset from GMT. Gah, stupid STUPID Sun engineers. |
| (0) Comments | Add Comment | |
| Quickies | |
|---|---|
|
Date: 2/3/2006 |
|
| (0) Comments | Add Comment | |
| Hardware | |
|---|---|
|
Date: 24/2/2006 | Ok, so the PC boots but the ongoing saga of stability took a new turn last night. In fit of morbid curiosity I pulled one of the memory sticks out of the machine, bringing it down to 256mb and did the usual video encode stress test overnight. It ran fine. And was still working in the morning. Currently the stock cooler fan is running about 3100rpm, the CPU is underclocked to 1.2ghz instead of 1.4ghz and it's voltage is stock. It ran at about 50 to 51° under load all night (12 hours straight).
I think the booting thing might have been related to having the fan speed set too low. Seems ok now. So I have one suspect memory stick. Great. I'll swap in the other one and run it all again tonight and see what happens. Hopefully it'll fail quickly and I can ditch the bad ram and move on. I've bid on a few name brand sticks on ebay... I have 3 slots anyway so I may as well use them. 512mb is starting to feel cramped on XP anyway. Update: Last night, back @ 1.4ghz again and the machine reset itself, and then this morning @ 1.33ghz the encode completed. So something is not happy at full speed. Maybe memory timing, the CL??? settings... hmmm I don't know. I guess I'll keep getting more sample points. Update2: I ran memtest86 with both sticks in and it errored out. So I pulled the motherboard manual and read the section on RAM. Turns out that slot "1" is the furthest from the CPU instead of the closest. Duh. So I moved the sticks into slots 1 and 2 instead of 2 and 3 and reset the timing to the correct default. And reran memtest86 at 1.2ghz overnight. No errors. Then the next night at 1.4ghz, no errors. Riiiight finally. Then last night it froze while printing. *bash head against wall* |
| (1) Comment | Add Comment | |