It's something I hacked up when I couldn't get SUS (predecessor to WSUS) to work, and seems to do the job.. only thing is, users need to have local admin if this is to run as a logon script.
There's been a fair bit of research on this kind of problem (read: it's been done before). Look around for a few papers on the operation of networks such as Tor, and both onion routing and anonymous remailers. Quite intriguing stuff.
Power loss doesn't depend on AC or DC in particular. However, they do have an effect on the ease at which power can be transformed to usable voltages. Now, back to high-school electronics..
Power loss is described as follows:
P = IV
V = I/R
P = I(I/R)
P = I^2/R
Resistance (in the wires) is pretty much fixed - we can't do much about that. However, we can do something about current. If we transform the power to an insanely high voltage (say, 300-500kV), we minimise transmission loss by reducing current (Remember, P = VI, and I is inversely proportional to V).
DC is harder to transform, but with switching power supplies over the last decade or so, it's become a viable method for power transmission, especially if we're talking trains.
I'd be guessing it's a notch filter at the beat frequency. GSM transmissions are notorious for this. That, and the shout-first, whisper-later protocol..
The tables I'm working on are definitely not within the public schema... although I do agree with you on the stored procedures. I'd log a bug with Postgres.. chuck it on the to-do list.
It features a PXA270 416MHz CPU, 64MB of RAM (work area), 4GB hard drive, 128MB of flash, 640 x 480 display (3.7"), SD card slot, Type2 CF slot, USB port, and infrared port. ....
The battery is a rechargeable lithium ion, with a constant display time of 7 hours (when displaying the calendar). The body size is 124 x 87 x 25mm (W x D x H), and it weighs about 298g
I bought an SL-C3100 (one of the newest models, released in October).. it's bloody brilliant. Combine it with OpenZaurus.. and it really shines. The Sharp firmware sucks balls though.
I worked with a guy who was talking about starting a business doing just that about 5-6 years ago.. not sure if it's the same mob or not; could very well be. Haven't seen any of the cars around though.. what parts of Melb have you seen them around?
Why implement the 'annoying' features? I'm sure many out there would share the same view as I.. scrap the bullshit features, and focus on the IM. Who needs graphical smileys, "winks", "nudges" etc etc.?
A client that doesn't appeal to the emo 14 year old teenagers is a good thing, IMHO.
Now, if only we could block AOL from the rest of the net...
Surgical enhancement of dolphin breasts.. I'd hate to think of the hydrodynamic effect.. then again, maybe they could sit on the surface and swim around like a catamaran..
Hate to discontinue the comedy thread in this article, but dolphins don't have breasts. The females do have two or four mammary slits either side of their genital slit, on the ventral side of their tail.
The only places I've worked at as yet are those with small development teams (1-3 people). Even then, the tendency's towards just firing off an email instead of documenting problems.
Self-control is a big thing when working in small teams, and enforcement of development policies important both in small and large teams.
I'd say you're right on the mark with the last sentence. All the quality developers seem to be moving away from those companies with bad software development practices, and towards those with an established set. Which leaves the industry in two halves - bad quality, bad developers, and good quality, good developers. The automotive industry I believe is moving towards the former.
Wasn't my choice at all. I only started there around 4 months ago; and it's been in use for a fair bit of time (c. 2002, from what I've heard from the other engineers). We're moving to Rational's VCS, but existing projects are sticking with VSS. It's not a good thing.
I can't give any solid info, but I can give a personal anecdote.
We recently had an 8gb VSS database corrupted, with about a quarter of the files unrecoverable. If you do use VSS, remember to do a -FREQUENT- analyse and fix on the database. And keep the database below 3gb - above this, you tend to get corruption issues.
Split your VSS database into managable chunks.. and (I'll repeat this again) don't allow your database to grow out of control, and not be maintained.
I'm sure you could find a few articles on Microsoft Support KBs to back this up.. just search for Sourcesafe and Analyse.
Slashdot Mirror
If you can't get WSUS to work (which is the best option around for free..), try this little script:
http://i3.tucuxi.org/articles/2005/hotfixes-wsh
It's something I hacked up when I couldn't get SUS (predecessor to WSUS) to work, and seems to do the job.. only thing is, users need to have local admin if this is to run as a logon script.
There's been a fair bit of research on this kind of problem (read: it's been done before). Look around for a few papers on the operation of networks such as Tor, and both onion routing and anonymous remailers. Quite intriguing stuff.
Yeah, that's more like it... caffeine was missing.
Power loss doesn't depend on AC or DC in particular. However, they do have an effect on the ease at which power can be transformed to usable voltages. Now, back to high-school electronics..
Power loss is described as follows:
P = IV
V = I/R
P = I(I/R)
P = I^2/R
Resistance (in the wires) is pretty much fixed - we can't do much about that. However, we can do something about current. If we transform the power to an insanely high voltage (say, 300-500kV), we minimise transmission loss by reducing current (Remember, P = VI, and I is inversely proportional to V).
DC is harder to transform, but with switching power supplies over the last decade or so, it's become a viable method for power transmission, especially if we're talking trains.
I'd be guessing it's a notch filter at the beat frequency. GSM transmissions are notorious for this. That, and the shout-first, whisper-later protocol..
The tables I'm working on are definitely not within the public schema... although I do agree with you on the stored procedures. I'd log a bug with Postgres.. chuck it on the to-do list.
Works for me via ODBC with both raw tables and views.
We considered osTicket for our project.. but one (minor?) setback - it's not available for download at present.
OTRS is the way to go.. been trialling it here with another person (two admins, ~200 users).. works a treat.
Well, this is completely off topic... but don't worry about the politically correct bullshit. I think most of us can take a comment or joke.
- http://www.techjapan.com/Article987.html
I bought an SL-C3100 (one of the newest models, released in October).. it's bloody brilliant. Combine it with OpenZaurus.. and it really shines. The Sharp firmware sucks balls though.
Would it be classified as a USB Human Interface Device? Can we get the USB Consortium to devise a common interface for this class of device?
Take a look at the Sharp Zaurus SL-C3100. I've got a friend with the C3000, and I'm strongly tempted to get one of the C3100s at the end of the year.
I worked with a guy who was talking about starting a business doing just that about 5-6 years ago.. not sure if it's the same mob or not; could very well be. Haven't seen any of the cars around though.. what parts of Melb have you seen them around?
I've found a link with a bit of information on what bitrate digital TV over CODFM achieves:
http://64.233.187.104/search?q=cache:wjCVgZM_gDgJ
Why implement the 'annoying' features? I'm sure many out there would share the same view as I.. scrap the bullshit features, and focus on the IM. Who needs graphical smileys, "winks", "nudges" etc etc.?
A client that doesn't appeal to the emo 14 year old teenagers is a good thing, IMHO.
Now, if only we could block AOL from the rest of the net...
Surgical enhancement of dolphin breasts.. I'd hate to think of the hydrodynamic effect.. then again, maybe they could sit on the surface and swim around like a catamaran..
Not my worry.. I'm not in the states. We don't have the feds looking up 'deviant porn'. Well, not officially, at least.
Hate to discontinue the comedy thread in this article, but dolphins don't have breasts. The females do have two or four mammary slits either side of their genital slit, on the ventral side of their tail.
The only places I've worked at as yet are those with small development teams (1-3 people). Even then, the tendency's towards just firing off an email instead of documenting problems.
Self-control is a big thing when working in small teams, and enforcement of development policies important both in small and large teams.
I'd say you're right on the mark with the last sentence. All the quality developers seem to be moving away from those companies with bad software development practices, and towards those with an established set. Which leaves the industry in two halves - bad quality, bad developers, and good quality, good developers. The automotive industry I believe is moving towards the former.
Wasn't my choice at all. I only started there around 4 months ago; and it's been in use for a fair bit of time (c. 2002, from what I've heard from the other engineers). We're moving to Rational's VCS, but existing projects are sticking with VSS. It's not a good thing.
Not quite what I was looking for, but rather interesting all the same.. thanks
I can't give any solid info, but I can give a personal anecdote.
We recently had an 8gb VSS database corrupted, with about a quarter of the files unrecoverable. If you do use VSS, remember to do a -FREQUENT- analyse and fix on the database. And keep the database below 3gb - above this, you tend to get corruption issues.
Split your VSS database into managable chunks.. and (I'll repeat this again) don't allow your database to grow out of control, and not be maintained.
I'm sure you could find a few articles on Microsoft Support KBs to back this up.. just search for Sourcesafe and Analyse.