|
You can buy USB-C(M) to USB-B(F) connectors on FleaBay - they are about 25mm long, and would fit on your existing cable(s). Not expensive either - I bought some recently by mistake (I wanted USB-C(F) to USB-A(M)) and they were £3 for five.
Don't ask. Just don't. 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: and they were £3 for five.
how many do you still have?
(gotta love the old n for $x marketing ploy when you really only need/can use one.)
hmmm, I'll use this one, and put the other 4 in a safe place.
either:
- lost (only found about a year after they become redundant while looking for something else)
or/and
- given today's chinesium production quality rot, leaving behind a toxic sticky mess (regardless climate.)
Message Signature
(Click to edit ->)
|
|
|
|
|
All five. Wrong bits ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Quote: (gotta love the old n for $x marketing ploy when you really only need/can use one.)
I just avoided buying four black toner cartridges for my old HP Colorjet. They worked out to be 25% cheaper each than if I bought just one. I bought just one.
I have had the printer for about eight years now and have just now needed to get a new black cartridge - extending this level of usage (and it's getting lower each year) means I avoided buying enough black toner for 32 years instead of only 8 years and saved spending almost three times as much for the privilege!
Eventually I might need to replace the other three colour cartridges - but not any time soon.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
very wise
8 years down the road had you even found [that really safe place] where the other 3 were kept chances are some insects or vermin would have moved in, and the plastics disintegrated too. (including the wrapping leaving a rock solid toner mountain and permanent stains below)
Message Signature
(Click to edit ->)
|
|
|
|
|
Most new USB-C type phones support fast charging, but your charger needs to support it, so take care which one you are using 
|
|
|
|
|
How much built-in RAM does it come with? And model number, please?
/ravi
|
|
|
|
|
I was inspired by this post to try one last time to 'fix' my 5 y/o Windows Phone. For months now, the micro USB slot has been screwed up so that I had to hold the cable in place with an elastic band to get it to charge...even then it was finicky and sometimes would come out.
When it first happened, I did what was suggested here, using a toothpick to clean the contacts and the slot. It didn't work so I figured the slot was just screwed. This morning, I decided to try something a bit thinner/stiffer, so I got a sewing needle and started poking around, immediately digging out what looked like hard packed dirt/dust. It took some force to get in the slot on the thin side, but I finally got it all out! Now the cables seat correctly. Problem solved! 
One of the things I had been missing was the ability to plug up to my pc and access the phone and SD card through explorer, so I tried that now and it did not work...the phone shows charging, but device not showing up in explorer. I tried another cable...no joy.  I found the original cable for the phone and tried it...and it worked! Apparently, not all micro-usb cables are the same. Yay! I don't need to get a new phone after all! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
|
...Total perspective[^]
Well, it made me laugh anyway.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I had a One. I like it.
.
.
.
.
I have a 3T. The camera stopped focusing the other day, hitting it on a hard surface like a concrete wall helps it to get its act together, for a short duration. Annoying. Wondering if the shoogling in the quad bike storage box has been the issue or if it is related to the common issue that is reported online. I had been holding off an upgrade just because it was working so well and nothing wrong with it, did everything I needed. Not now.....
.
.
.
.
I have ordered a 7 Pro, 12GB ram, 256GB storage, Nebula Blue
|
|
|
|
|
DaveAuld wrote: shoogling in the quad bike storage box
Does this refer to a sex act ?
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
He can only answer that if:
1. It is not a sex act (shoogling just means shaking).
..or..
2. He takes it to the Soapbox, hmmm..
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
|
adding it to the rotation. My favorite indie band is The Mountain Goats, and probably one of my favorite songs, despite being under two minutes long and super simple and beautiful:
Genesis 19:1-2
The Mountain Goats - Genesis 19: 1-2 - YouTube[^]
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I love Chasing Cars, despite having some bad memories to it (which all turned out alright).
This one sounds really good too.
I guess I have me some Snow Patrol to listen to 
|
|
|
|
|
Our products generate a "diagnostic report" which lists all of the system and Windows information you could ever want to know about a machine. We're testing a new model of industrial PC, and the diagnostic report was failing while it was enumerating the device drivers installed.
The Intel chip-set drivers for this new, fancy-schmancy motherboard (dual Xeon's, 64GB RAM, 10GB ethernet) report creation dates in... 1968(*). Yes ladies and gentlemen, these drivers were written under the influence of some really trippy acid during the Summer of Love .
(*) A FILETIME value passed to a CTime constructor, which promptly throws an exception because the date/time is out of range for the underlying time_t value, based on the UNIX 1/1/1970 epoch date.
Software Zen: delete this;
|
|
|
|
|
At Intel they must be di-agnostic
|
|
|
|
|
Maybe it wasn't broken.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Hi,
Gary Wheeler wrote: The Intel chip-set drivers for this new, fancy-schmancy motherboard (dual Xeon's, 64GB RAM, 10GB ethernet) report creation dates in... 1968
I just looked at all of the possible epochs. I can't even come up with any conversion math that would cause a 50 year offset.
What date are you looking at? NTFS file creation date? Code signing date? PE VERSIONINFO block date?
Best Wishes,
-David Delaune
|
|
|
|
|
oh hell. that must have been fun to track down.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Running under the debugger it was easy. A CTime constructor was throwing an exception. The date/time value was of the type FILETIME, which has a much broader range than that allowed by the time_t (32-bit) that underlies CTime.
Unfortunately since this is C++ code most of my bugs are far more difficult to find. Our application is multiple processes (a UI app and some services) and each process is heavily multithreaded. Even the UI app has 50+ threads running. This means that there can be significant differences in behavior between debug compiles at my desk vs. release compiles in the product due to timing, heap checking, and so on.
Software Zen: delete this;
|
|
|
|
|
> Even the UI app has 50+ threads running
That seems... not okay.
But I'm sure you have your reasons.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
It does sound unusual but... Obviously, we have a main application thread running the UI window itself and the corresponding message loop. There are several threads handling network communications with underlying services and our tracing/diagnosis tool. Any number of background threads in the UI app and the services may be performing or monitoring external physical processes. Over the last 20 years, our programming model for our products has become quite adept at handling a multi-process/multi-threaded implementation. It's relatively rare that we find a bug arising from a deadlock or resource contention issue. Our bugs now tend to be problems in the physical processes and our control/monitoring of them.
Software Zen: delete this;
|
|
|
|
|
That's impressive, although I have to wonder about the efficiency of creating all those threads. I'm curious if you pool - but not surprised if NDA prevents you from discussing it further.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
