Quote from: cwpab on Today at 18:50Is there any possible explanation to why this happens in Windows 11, but not in Windows 10? (Maybe I should try creating a folder with those names from the CLI?)It does happen in all versions of Windows. I think the NT line always had ways of getting around it if you really wanted to create yourself headaches (using NTFS native paths for example) but Explorer always had a prompt to block you.
I mean, if they are supposedly "dragging" this from 35 years ago, shouldn't this also be an issue in ALL versions of Windows and not just in 11?
Quote from: Bryce on Today at 13:50Check the flat cable to the driveWill do. Thx.
Quote from: Bryce on Today at 13:50Also check the drive PCB (especially the sockets) for dry joints.on the drive? I checked with another drive which definitely works and it has the same issues, so it probably is the 664. Or do you mean the sockets of the ICs on the 664 PCB?
Quote from: GUNHED on Today at 15:30Pretty far fetched to blame CP/M for a Windows 11 symptome.It's not really blaming CP/M, it's just a historic fact. MSDOS took the concept from CP/M to preserve compatibility, Windows inherited it from DOS to maintain compatibility....
Page created in 0.026 seconds with 17 queries.