Subject: Re: A simple way to transfer photos from your phone to Windows without installing anything on either
> One series of threads I could find, blamed the cause on
> Ubuntu is just not building gcc with -D_FILE_OFFSET_BITS=64
> which causes 64-bit routines for file parameters to be use automatically.
Hmmmmmmmmm.... thanks for finding that Paul, which may mean that I
accidentally used a 32-bit Knoppix. I will have to check the Knoppix
because I didn't write on the DVD disc whether it was 32-bit or 64-bit
where I got Knoppix from this torrent.
> Since you say you're staying "on-platform" and not using
> SAMBA/CIFS for this transfer, the result is highly
Yup. No big deal though, because I bought a SATA III 6GB SATA cable plus a
4-pin Molex male to dual SATA female set of cables today, and now have
/both/ HDDs in the desktop where Windows is booting from SATA1 and the DVD
drive is on SATA2 with the bad boot HDD on SATA3..
The bad-boot HDD seems to show up just fine in Windows as a non-boot data
drive, so I shouldn't need Knoppix, which I only used because I wanted to
back up my data BEFORE giving it to the Microsoft Retail Store genius bar
employees to fix.
> I've never seen this error in all the times
> I've tried things with various Linux distros. I might
> even be convinced to run a memory test as my first step
The Microsoft Genius Bar retail store employees said they checked
everything, and it all checked out fine (memory, HDD, etc.). It was just
bricked. I asked specifically what they did, and they said they ran machine
diagnostics first, and then they booted to the X: drive (as we did in the
past) where they ran something they called bcdedit, fixboot, & scanos.
They said they tried to fix the master boot record (fixboot) and even tried
older versions of Windows 10 in addition to the Fall Creator's Update.
> After the memtest completed one pass successfully,
> I would change distros. And move on.
I have the problem mostly solved since the Microsoft genius bar employees
couldn't get it to boot, so, the updated and bricked Windows 10 Pro OS is a
write off but everything else appears to be fine.
Thanks for all your kind and expert help. It turns out that the OS was
bricked by the late January Microsoft Windows 10 Pro Update, where two
different employees at the store (once when I dropped it off, and again
when I picked it up, asking the same question) told me they get this at
least once a day, sometimes a few times a day, so it's pretty common in the
real world for a Windows 10 Update to brick the system.