User forums > Help
usb device disabled after installing code blocks
MortenMacFly:
--- Quote from: Neil Butterworth on January 30, 2012, 12:37:16 am ---How in hell's name can installing a compiler disable a device?
--- End quote ---
Sorry, but this is actually not possible. Only, if i.e. an installer overwrites system DLL's used by Windows. But for C::B this is not the case and even if, the Windows file protection (starting with XP) would "fix" this immediately. So actually I can only hardly believe this. What the C::B installer does is nothing else than copying files into a single folder. No files are put into system folders, no PATH environment variables is touched, no components are registered, no registry hacks are applied.
I am 99.9% sure the reason is somewhere else. What else did you install? Updates? Maybe there was a pending update that required a system restart which you did?
Jenna:
It was not an overwritten usb-drive, but MinGW complaining about a missing drive, that was present when builing MinGW.
I am not sure, if this was the case for the MinGW version provided with 10.05.
And we all (windows users) know, that the windows usb-drive management is poor (or at least was poor on xp and most likely vista), so it was a wild guess of mine, that there went something wrong with it.
And if it is really the case and not just a "funny" coincidence, it is either windows or the usb-board (and its drivers) which is to blame in my opinion.
Navigation
[0] Message Index
[*] Previous page
Go to full version