Displaying 3 results from an estimated 3 matches for "jan2004".
Did you mean:
jan2003
2011 Jan 16
2
xyplot: modify axis tick marks
...8
Mar2002 55.6
Apr2002 116.5
May2002 236.6
Jun2002 83.1
Jul2002 233.7
Aug2002 54.2
Sep2002 124.2
Oct2002 10.8
Nov2002 307.2
Dec2002 255
Jan2003 444.2
Feb2003 172.9
Mar2003 154.6
Apr2003 159.9
May2003 81.8
Jun2003 50.3
Jul2003 170.4
Aug2003 193.6
Sep2003 205.3
Oct2003 351.4
Nov2003 133.8
Dec2003 273
Jan2004 600.9
Feb2004 31.9
Mar2004 269.4
Apr2004 57.1
May2004 137.6
Jun2004 127.2
Jul2004 166.6
Aug2004 185.2
Sep2004 128.9
Oct2004 125.6
Nov2004 166.2
Dec2004 139.8
Jan2005 163.2
Feb2005 8.4
Mar2005 82.4
Apr2005 81.7
May2005 331.1
Jun2005 82.3
Jul2005 104
Aug2005 58.5
Sep2005 175.7
Oct2005 314.5
Nov2005 3...
2005 Aug 19
1
Sustainer S-1000C (Powercom protocol)
...aven't managed to make NUT work with it. When I tried using
the powercom driver, I got the following response, no matter which type I
entered (including the KIN1500AP I've seen on the wayback machine had the
same problem -
http://web.archive.org/web/20041020015206/lists.exploits.org/ups/Jan2004/00003.html):
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.1
Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision:
0.5 $ (2.0.1)
data receiving error (-1 instead of 11 bytes)
Running the driver itself on KIN-1500AP with debug:
/lib/nut# ./powercom -D -x type...
2005 Jul 30
0
Sustainer S-1000C
...aven't managed to make NUT work with it. When I tried using
the powercom driver, I got the following response, no matter which type I
entered (including the KIN1500AP I've seen on the wayback machine had the
same problem -
http://web.archive.org/web/20041020015206/lists.exploits.org/ups/Jan2004/00003.html):
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.1
Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision:
0.5 $ (2.0.1)
data receiving error (-1 instead of 11 bytes)
Running the driver itself on KIN-1500AP with debug:
/lib/nut# ./powercom -D -x type...