Forgot your password?

Comment: Re:Computer Missues Act 1990 (Score 1) 572

by djdanlib (#48222177) Attached to: FTDI Removes Driver From Windows Update That Bricked Cloned Chips

The problem with that, as I understand it: On Windows, you can change the drivers' INF files to use PID 0 with any text editor. You could do something similar on any OS. The problem is, the OS won't even try to load drivers for devices with PID 0. So you can't write a driver for that unless you intend to write a new driver for the USB chipset itself that remaps PID 0 devices to something else.

Comment: Whose job is it to know that? (Score 1) 313

by djdanlib (#48183493) Attached to: If You're Connected, Apple Collects Your Data

Why is Apple even responsible for tracking that kind of information?

Can I sue them if they get it wrong, rendering my mail client unable to connect to the correct server (or revealing my credentials to a third party) because it followed their instructions instead of mine? No, that wasn't a typo, but thank you for redirecting my login credentials to the wrong server, which then stole them and used them...

Comment: Re:Mind boggling (Score 3, Insightful) 167

by djdanlib (#47979193) Attached to: Now That It's Private, Dell Targets High-End PCs, Tablets

Wellllll... kind of. When you're publicly traded, it's all about risk and paring down excesses. Shareholders don't want you to take risks. They want you play it safe so their share values don't go down. They want to see that you've cut operating expenses by X in every report. This limits your ability to try new things or market to those niches.

When you're private, you can take as big of a risk as your cash reserves permit.

Comment: I have a solution for impacted users (Score 5, Informative) 179

by djdanlib (#47671791) Attached to: Microsoft Black Tuesday Patches Bring Blue Screens of Death

This rollback procedure got my Win7 x64 system booting again:

From another system with the same bit width and service pack level, grab the files C:\Windows\System32\gdi32.dll and C:\Windows\System32\Win32k.sys.

Using HBCD or a similar boot disc, boot your defunct system. You can also snag the hard drive and plug it into another working computer.

BACK UP the gdi32.dll and win32k.sys files from System32 to another location just in case. Overwrite those two files in System32 with the ones you grabbed from the other system.

Your system is now bootable, having effectively rolled back the KB2982791 update. This is a quick and dirty procedure and leaves the update itself in an indeterminate state.

Innovation is hard to schedule. -- Dan Fylstra