What is a DC ground and what is a AC outlet pin?
DC ground is the ground level reference on typical computer and
peripheral devices, including the metal portion of USB plugs and
sockets' shells. If that doesn't explain it well enough, it is beyond
the scope of a usenet topic to review basic electronics design when
the internet is available and more thorough than a usenet post could
be.
AC outlet pin is simply the ac outlet in your wall, one of those holes
in it has a metal contact that could be referred to a number of ways,
including a pin.
AC ground is referenced (attempts to attain the same voltage level) as
earth ground, to have 0.0V difference between it and earth ground.
However with some devices there is no connection to earth ground, they
have what can be called a floating ground meaning their ground voltage
is independant of earth ground, may be positive or negative relative
to earth ground without it being a problem. Take for example a
battery powered radio. The negative terminal of the battery connects
to ground in that piece of equipment, but it is floating if there is
no electrical connection between it and earth ground, earth ground
really meaning "earth", soil, through water pipes or the wall outlets
in your home if they were properly wired.
I am using "ordinary" two-pinned plugs in ordianry ungrounded sockets.
Ok, but the most important thing you did not answer, what the supplies
for these devices are like. Do t hey use a 3 pin cord, and you have
outlets with the ground hole, or 3 pin and you have to use an adapter
to make them fit in your 2 pin outlet, or do they use only 2 pin
plugs? If they use 2 pin plugs, they aren't trying to by design,
don't need to ground themselves.
I don't think a clean install of Vista will help as the printer driver
was installed on a brandnew, clean desktop with a freshly installed
Vista.
You might be right, or the conclusion might be premature. It's also
possible there are patches that improve OS functions broken, or
patches that broke things which previously worked. The ultimate goal
is to leave no variables unexplored and the OS is certainly one of
those variables. If you only assume something can't be wrong, it can
waste a lot of time trying other things. Even so, you know better
than us what the state is of everything there, installing an OS and
reconfiguring it does take longer than other attempts so it makes
sense to try other things first.
According to Canon I am using the right driver for a 64-bit system.
Ok, but being the "right" driver doesn't necessarily mean there isn't
something wrong with that driver, if it has a design defect, a bug
interfering with it working properly. This is quite commonly the
case with the first few revisions of a driver for a new(er) OS, or a
new product on an old OS, upon which they didn't do enough testing.