I was trying to install hauppage pvr150mce, a biatch of a device because it may not output sound. I install, uninstal many times, then the sound disappeared.
The solution is here:
http://www.techsupportforum.com/microsoft-support/windows-xp-support/368757-no-sound-drivers-installed-no-conflicts-but-hardware-not-seen-software.html
this was not the site that I used but i think its the same. the part about the swenum.sys was not necessary. Just copy the machine.inf , mod the machine.inf then add new hardware.
I don't know how the hell this guy figured it out but thanks, heaps.
Friday, July 31, 2009
trying to buildroot
Boy another pain in the neck. This thing has so many build options, something is bound to go wrong, and it does. I'm still trying to build it after 3-4 days!
It has to download then all the incomplete dependencies/combo. What a nightmare.
to get past vm86:
It has to download then all the incomplete dependencies/combo. What a nightmare.
to get past vm86:
See https://bugs.gentoo.org/show_bug.cgi?id=235789
2008-09-09 Martin von Gagern
--- xorg-server-1.5.0.orig/hw/kdrive/vesa/vm86.h 2008-09-09 17:24:59.000000000 +0200
+++ xorg-server-1.5.0/hw/kdrive/vesa/vm86.h 2008-09-09 18:01:53.000000000 +0200
@@ -67,6 +67,13 @@
#include "os.h"
#endif
+#ifndef IF_MASK
+#define IF_MASK X86_EFLAGS_IF
+#endif
+#ifndef IOPL_MASK
+#define IOPL_MASK X86_EFLAGS_IOPL
+#endif
+
typedef unsigned char U8;
typedef unsigned short U16;
typedef unsigned int U32;
Don't forget to add wchar (or wide char) support at the top level (and if not propergate to uClibc)
there as well. Also large file support is good too.
APE is crap again
I find that the JSF side is a little unreliable on firefox/linux (haven't tried any other combo). Sometimes (50%) it doesn't join the channel. ???
Why, donno.
Maybe I should reverse engineer anyterm. At least it's a better use of my time than this shite.
Why, donno.
Maybe I should reverse engineer anyterm. At least it's a better use of my time than this shite.
Sunday, July 26, 2009
i've been hit by ... i've been hit by ... win32:vitro win32:virut
yes a smooth criminal indeed.
I have been hit by this evil virus. Reminds me of something I got ages ago and couldn't remove and had to not trust anything in my old archives until a scanner can definitely detect it. Avast is the only thing that can detect post infection but not during running as it seems to still spread even with avast running! Better than nothing. It's now doing a scan and boy basically all the exe's are infected. I'm glad there's laws for virus creators, we just have to catch the b*****d.
So now I have to do the same thing. Install windows and download everything again. I'll prolly have to zip password my new backups and sum archive a list. Man dotnet, SP3 and SFU are huge files.
I have been hit by this evil virus. Reminds me of something I got ages ago and couldn't remove and had to not trust anything in my old archives until a scanner can definitely detect it. Avast is the only thing that can detect post infection but not during running as it seems to still spread even with avast running! Better than nothing. It's now doing a scan and boy basically all the exe's are infected. I'm glad there's laws for virus creators, we just have to catch the b*****d.
So now I have to do the same thing. Install windows and download everything again. I'll prolly have to zip password my new backups and sum archive a list. Man dotnet, SP3 and SFU are huge files.
Friday, July 24, 2009
at last I fixed it
After hours of reading, learning javascript, mootools, firebugging, wiresharking, ddd, gdb it works. It's exactly what I wanted but what a way to learn it. Anyways below is what I used to get a working controller demo working.
First the apache configuration. I got this from someones post, something about APE on ubuntu, see http://www.blogger.com/post-create.g?blogID=1847386878976174462.
Here's my apache config:
create
/etc/apache2/sites-available/ape.conf
Contents:
<VirtualHost *:80>
ServerName ape.ape-test.local
ServerAlias *.ape.ape-test.local
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass / http://localhost:6969/
ProxyPassReverse / http://localhost:6969/
</VirtualHost>
Then run the following to enable the config
sudo a2ensite ape.conf
Then restart apache
sudo /etc/init.d/apache2 restart
Put the demo into a directory served by apache, loading the script is another missing part.
demo.html:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" dir="ltr" lang="en">
<head>
</head>
<body>
<script type="text/javaScript" src="../../Clients/mootools-core.js"></script>
<script type="text/javaScript" src="../../Clients/MooTools.js"></script>
<script type="text/javaScript" src="../config.js"></script>
<script type="text/javaScript" src="demo.js"></script>
<script type="text/javaScript">
var client = new APE.Client();
var debug=true;
client.load({
identifier: 'mailnotif',
channel: 'testchannel',
complete: function(ape){
var ape_c = new APE.Controller(ape, {container: $('ape_master_container')});
},
'scripts': APE.Config.scripts //Scripts to load for APE JSF
});
</script>
To try this demo, you need :
<ul>
<li>mod controller on APE server enabled</li>
<li>mod chat on APE server disabled</li>
<li>Set your APE server adresse in the controller/test.php</li>
</ul>
Then load this page and go to <a href="./test.php" target="_blank">controller/test.php</a> and you will see a message appear here.
<br/>
<br/>
<div id="ape_master_container" style="border:1px solid #000;padding:10px;background:#CCC;"></div>
<div id="debug"></div>
</body>
</html>
My demo.js, the join is the important missing part. It creates the channel.
APE.Controller = new Class({
Implements: [APE.Client, Options],
options:{
container: null,
logs_limit: 10
},
initialize: function(core, options){
this.core = core;
this.setOptions(options);
this.options.container = $(this.options.container) || document.body;
this.els = {};
this.onRaw('mailnotif', this.raw_data);
this.core.start();
// this.core.join('testchannel')
},
init: function() {
this.core.join('testchannel');
},
raw_data: function(raw, pipe){
new Element('div', {
'class': 'css_class',
'html': decodeURIComponent(raw.datas.value)
}).inject(this.options.container);
}
});
The ../config.js, the inclusion of mootools-core was missing as it defined the 'Class'. Also why the f*** is there 2 mootools-core? One in the Source directory and the other in Client, and they are different! Why not follow the common sense rule of using different names?
APE.Config.baseUrl = 'http://ape-test.local/jpscc/APE_JSF/Source'; //APE JSF
APE.Config.domain = 'ape-test.local'; //Your domain, must be the same than the domain in aped.conf of your server
APE.Config.server = 'ape.ape-test.local'; //APE server URL
//Scripts to load for APE JSF
(function(){
for (var i = 0; i < arguments.length; i++)
APE.Config.scripts.push(APE.Config.baseUrl + '/' + arguments[i] + '.js');
})('mootools-core','Core/Events', 'Pipe/Pipe', 'Pipe/PipeProxy', 'Pipe/PipeMulti', 'Pipe/PipeSingle', 'Core/Core', 'Core/Utility','Core/Session');
the /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.0.1 0.ape.ape-test.local
127.0.0.1 1.ape.ape-test.local
127.0.0.1 2.ape.ape-test.local
127.0.0.1 3.ape.ape-test.local
127.0.0.1 4.ape.ape-test.local
127.0.0.1 5.ape.ape-test.local
127.0.0.1 6.ape.ape-test.local
127.0.0.1 7.ape.ape-test.local
127.0.0.1 8.ape.ape-test.local
127.0.0.1 9.ape.ape-test.local
127.0.0.1 10.ape.ape-test.local
127.0.0.1 11.ape.ape-test.local
127.0.0.1 12.ape.ape-test.local
127.0.0.1 13.ape.ape-test.local
127.0.0.1 14.ape.ape-test.local
127.0.0.1 15.ape.ape-test.local
127.0.0.1 *.ape.ape-test.local
127.0.0.1 ape.ape-test.local
127.0.0.1 ape-test.local
Finally test.php
<?php
$ape_server = 'http://0.ape.ape-test.local';
file_get_contents($ape_server.'/?control&testpwd&testchannel&POSTMSG&mailnotif&testmsg&anticache');
echo 'Message sent!';
?>
Or if you prefer:
wget -c "http://0.ape.ape-test.local//?control&testpwd&testchannel&POSTMSG&mailnotif&hello_there&anticache"
There, that should work if I didn't miss anything. Phew all this just to scroll output from the console into a web page. APE doco and demo sucks but hope this helps you.
First the apache configuration. I got this from someones post, something about APE on ubuntu, see http://www.blogger.com/post-create.g?blogID=1847386878976174462.
Here's my apache config:
create
/etc/apache2/sites-available/ape.conf
Contents:
<VirtualHost *:80>
ServerName ape.ape-test.local
ServerAlias *.ape.ape-test.local
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass / http://localhost:6969/
ProxyPassReverse / http://localhost:6969/
</VirtualHost>
Then run the following to enable the config
sudo a2ensite ape.conf
Then restart apache
sudo /etc/init.d/apache2 restart
Put the demo into a directory served by apache, loading the script is another missing part.
demo.html:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" dir="ltr" lang="en">
<head>
</head>
<body>
<script type="text/javaScript" src="../../Clients/mootools-core.js"></script>
<script type="text/javaScript" src="../../Clients/MooTools.js"></script>
<script type="text/javaScript" src="../config.js"></script>
<script type="text/javaScript" src="demo.js"></script>
<script type="text/javaScript">
var client = new APE.Client();
var debug=true;
client.load({
identifier: 'mailnotif',
channel: 'testchannel',
complete: function(ape){
var ape_c = new APE.Controller(ape, {container: $('ape_master_container')});
},
'scripts': APE.Config.scripts //Scripts to load for APE JSF
});
</script>
To try this demo, you need :
<ul>
<li>mod controller on APE server enabled</li>
<li>mod chat on APE server disabled</li>
<li>Set your APE server adresse in the controller/test.php</li>
</ul>
Then load this page and go to <a href="./test.php" target="_blank">controller/test.php</a> and you will see a message appear here.
<br/>
<br/>
<div id="ape_master_container" style="border:1px solid #000;padding:10px;background:#CCC;"></div>
<div id="debug"></div>
</body>
</html>
My demo.js, the join is the important missing part. It creates the channel.
APE.Controller = new Class({
Implements: [APE.Client, Options],
options:{
container: null,
logs_limit: 10
},
initialize: function(core, options){
this.core = core;
this.setOptions(options);
this.options.container = $(this.options.container) || document.body;
this.els = {};
this.onRaw('mailnotif', this.raw_data);
this.core.start();
// this.core.join('testchannel')
},
init: function() {
this.core.join('testchannel');
},
raw_data: function(raw, pipe){
new Element('div', {
'class': 'css_class',
'html': decodeURIComponent(raw.datas.value)
}).inject(this.options.container);
}
});
The ../config.js, the inclusion of mootools-core was missing as it defined the 'Class'. Also why the f*** is there 2 mootools-core? One in the Source directory and the other in Client, and they are different! Why not follow the common sense rule of using different names?
APE.Config.baseUrl = 'http://ape-test.local/jpscc/APE_JSF/Source'; //APE JSF
APE.Config.domain = 'ape-test.local'; //Your domain, must be the same than the domain in aped.conf of your server
APE.Config.server = 'ape.ape-test.local'; //APE server URL
//Scripts to load for APE JSF
(function(){
for (var i = 0; i < arguments.length; i++)
APE.Config.scripts.push(APE.Config.baseUrl + '/' + arguments[i] + '.js');
})('mootools-core','Core/Events', 'Pipe/Pipe', 'Pipe/PipeProxy', 'Pipe/PipeMulti', 'Pipe/PipeSingle', 'Core/Core', 'Core/Utility','Core/Session');
the /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.0.1 0.ape.ape-test.local
127.0.0.1 1.ape.ape-test.local
127.0.0.1 2.ape.ape-test.local
127.0.0.1 3.ape.ape-test.local
127.0.0.1 4.ape.ape-test.local
127.0.0.1 5.ape.ape-test.local
127.0.0.1 6.ape.ape-test.local
127.0.0.1 7.ape.ape-test.local
127.0.0.1 8.ape.ape-test.local
127.0.0.1 9.ape.ape-test.local
127.0.0.1 10.ape.ape-test.local
127.0.0.1 11.ape.ape-test.local
127.0.0.1 12.ape.ape-test.local
127.0.0.1 13.ape.ape-test.local
127.0.0.1 14.ape.ape-test.local
127.0.0.1 15.ape.ape-test.local
127.0.0.1 *.ape.ape-test.local
127.0.0.1 ape.ape-test.local
127.0.0.1 ape-test.local
Finally test.php
<?php
$ape_server = 'http://0.ape.ape-test.local';
file_get_contents($ape_server.'/?control&testpwd&testchannel&POSTMSG&mailnotif&testmsg&anticache');
echo 'Message sent!';
?>
Or if you prefer:
wget -c "http://0.ape.ape-test.local//?control&testpwd&testchannel&POSTMSG&mailnotif&hello_there&anticache"
There, that should work if I didn't miss anything. Phew all this just to scroll output from the console into a web page. APE doco and demo sucks but hope this helps you.
Wednesday, July 22, 2009
APE (ajax push engine) is shite
yes I was hoping to use some nifty (hopefully) asynchronous streaming using this shit but what I got was days of aggravation.
Yeah you will know something (as I have not finished yet) but from their lack of any useful documentation and their crappy demos which don't work. I'm trying to debug the bastard to see what's going on.
I'M STILL DEBUGGING!
Please god give me an alternative that does work! Somebody!
Yeah you will know something (as I have not finished yet) but from their lack of any useful documentation and their crappy demos which don't work. I'm trying to debug the bastard to see what's going on.
I'M STILL DEBUGGING!
Please god give me an alternative that does work! Somebody!
Friday, July 3, 2009
Greenspan are assholes
We recently received a document from these people. It was a simple request for data exchange. We got it but we also got some personal shit about our project. It was not part of what we asked of them. The comments basically said that our contractor was incompetent and our data was no good. They had no proof no real technical assessment and yet they threw this in to make them look good. It gave the impression that they were 'professional' and were somehow qualified whereas we are just monkeys in the jungle.
Do they know what equipment we used, our sensors. What the output is? No.
The output for wind is 4-20mA, why? because its more tolerant. Regardless of what is between the sensor and the datalogger the output will be 4-20mA. Same with soil moisture, nothing is gonna effect the frequency between the sensor and the logger. The water quality? It all digital!
Only voltage output is where it is most tricky.
This is what you can expect from Greenspan. Don't bother with condescending people like these.
Do they know what equipment we used, our sensors. What the output is? No.
The output for wind is 4-20mA, why? because its more tolerant. Regardless of what is between the sensor and the datalogger the output will be 4-20mA. Same with soil moisture, nothing is gonna effect the frequency between the sensor and the logger. The water quality? It all digital!
Only voltage output is where it is most tricky.
This is what you can expect from Greenspan. Don't bother with condescending people like these.
Thursday, July 2, 2009
ubuntu live ... finally
I was scratching like crazy to find why I cannot just copy the casper-rw the casper directory and the .disk files n dirs into a partition and tell grub to boot it. It works but it wasn't persistent.
Now after debugging the casper script I have found the solution but not tested yet. Have to wait till I get home. It's this line in casper-helpers in the find_cow_device function
elif [ "$(get_fstype ${devname})" = "vfat" ]; then # FIXME: all supported block devices should be scanned
Funny how the fixme is actually the solution to the problem. What I had done is placed the casper-rw file on an ext3 partition. The loader only caters for the vfat file system. The solution is to add a condition when the persistent file is in an ext3 partition. Quick hack is to change the vfat to ext3, a better solution is to copy the 10 lines and change the vfat to ext3 or add an 'or' condition to the test.
That should fix it. Can't wait to go home or the office.
Now after debugging the casper script I have found the solution but not tested yet. Have to wait till I get home. It's this line in casper-helpers in the find_cow_device function
elif [ "$(get_fstype ${devname})" = "vfat" ]; then # FIXME: all supported block devices should be scanned
Funny how the fixme is actually the solution to the problem. What I had done is placed the casper-rw file on an ext3 partition. The loader only caters for the vfat file system. The solution is to add a condition when the persistent file is in an ext3 partition. Quick hack is to change the vfat to ext3, a better solution is to copy the 10 lines and change the vfat to ext3 or add an 'or' condition to the test.
That should fix it. Can't wait to go home or the office.
Subscribe to:
Comments (Atom)
