A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

A simple way to transfer photos from your phone to Windows without installing anything on either



 
 
Thread Tools Rate Thread Display Modes
  #16  
Old February 24th 18, 09:52 PM posted to rec.photo.digital,alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default A simple way to transfer photos from your phone to Windows withoutinstalling anything on either

ultred ragnusen wrote:
Paul wrote:

Once I burn the ISO to a disk will it be 'bootable' or will additional
action be required first?

It requires dancing a jig on one foot.


The Tier 2 Microsoft support person at +1-800-642-7676 took control of
another Windows 10 Pro system to download, burn, test, and run the same
sequence of repair that we ran (and failed at) using the bricked Windows 10
Pro recovery console.
http://wetakepic.com/images/2018/02/...dvd_repair.jpg

For the data, Knoppix worked just fine, but I am getting a very common
error from Knoppix on files that shouldn't have that error, where, when I
google for the error, NONE of the common causes can possibly be why I'm
getting that error.
Error splicing file: Value too large for defined data type.
http://wetakepic.com/images/2018/02/...x_error_01.jpg


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.
You can declare such things discretely when programming, or
taking a legacy program and passing -D_FILE_OFFSET_BITS=64
helps in an attempt to fix them automatically.

*******

https://bugs.launchpad.net/ubuntu/+s...ts/+bug/455122

The inode number in the example, is huge.

# on cifs mount...
19656 open("grape.c", O_RDONLY|O_NOCTTY) = 3
19656 fstat64(3, {st_dev=makedev(0, 23), st_ino=145241087983005616, === not a normal inode
st_mode=S_IFREG|0755, st_nlink=1, st_uid=3872,
st_gid=1000, st_blksize=16384, st_blocks=1, st_size=25,
st_atime=2009/10/18-19:13:16, st_mtime=2009/10/18-19:00:51,
st_ctime=2009/10/18-22:31:53}) = 0
19656 close(3) = 0

If we convert that number to hex, it's 0x020400000004AFB0.
It's remotely possible the inode number is actually 4AFB0
and the upper portion is "noise" from an uninitialized
stack parameter or memory location.

That's probably not the only root cause, but I wanted
to at least see an example of what they might be
complaining about.

In Linux, when NTFS is mounted, stat() results are faked
to make Linux "comfortable" with the IFS being mounted.
The Linux inode number, is actually formulated using
the #filenum of a file from $MFT. So the parameter in
fact, has a traceable origin. If you saw the errant
inode number in that case, you might be able to look up
in the $MFT, and see a "match" for the lower portion
of the number (the 4AFB0 part).

Since you say you're staying "on-platform" and not using
SAMBA/CIFS for this transfer, the result is highly
unusual. 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
(memtest86+).

After the memtest completed one pass successfully,
I would change distros. And move on.

*******

The other possibility, is the source disk is damaged
somehow. But the way Windows handles filenum, it doesn't
allow the number to grow and grow. When you delete a file,
the "slot" is available for the next file creation. This
helps to keep the "epoch" of filenum values low. While
the filenum field is likely to be a large one (to suit
the declared maximum number of files that NTFS supports
in Wikipedia), users probably never see filenum
values remotely approaching the max_value.

On my Win10 C: drive with the build trees in the user folder,
the stats (as collected by the old Win2K era utility nfi.exe) are

Number of files: 1318185

Last file:

File 1341804

\Windows\servicing\Version\10.0.16299.245

So the highest #filenum (1341804) is not even remotely close
to being a 64 bit number in magnitude. And I don't even know
if a corruption on the source side could be interpreted that
way.

Paul
Ads
  #17  
Old February 25th 18, 02:40 AM posted to rec.photo.digital,alt.windows7.general
Mike S[_4_]
external usenet poster
 
Posts: 496
Default A simple way to transfer photos from your phone to Windowswithout installing anything on either

On 2/24/2018 11:01 AM, ultred ragnusen wrote:
Mike S wrote:

You can do a startup repair and then a complete 10 repair install with a
free w10 dvd (you d/l the iso for).


This Windows 10 Pro update bricking happened just after the first reboot of
the system after 3 consecutive sets of daily failed Windows 10 software
updates on the 25th, 26th, and 27th of January.
http://wetakepic.com/images/2018/02/...update_010.jpg

w10 disk image
https://www.microsoft.com/en-us/soft...load/windows10


The Microsoft Tier2 telephone technical support (+1-800-642-7676) tried all
the Windows recovery options (save one) from the bricked boot disk, all of
which failed.
http://wetakepic.com/images/2018/02/...tup_repair.jpg

Microsoft telephone support also tried the same set of all but one recovery
options using a DVD that he downloaded and burned for me when I gave him
control over a good Windows 10 desktop.
http://wetakepic.com/images/2018/02/...dvd_repair.jpg

If you can't boot from the hdd, boot from the dvd and run the startup
repair.


That fails because Microsoft Windows 10 Pro update bricked the OS.
http://wetakepic.com/images/2018/02/24/reset_pc_02.jpg

If that is successful and you can boot from the hdd you can
reinstall all of the w10 system files while retaining your programs,
settings, and data, if needed.


I already bought a new HDD and installed Windows 10 Pro and even had
Microsoft Software Specialists install for me Office 2007 Pro over the
phone by taking over control of my system yesterday.

SOLVED: How to download an ISO image for Office 2007 Pro in the year 2018
https://groups.google.com/forum/#!to...al/7ru4_AyhPCY

http://wetakepic.com/images/2018/02/24/reset_pc_04.jpg

w10 repair install procedure
https://neosmart.net/wiki/windows-10...-installation/


The data is the only thing I care about since programs and operating
systems are all free (sort of) and readily available.

For the data, I'm trying the various methods (Knoppix, Testdisk, Recuva,
PhotoRec, DDRescue, etc.) all of which have much promise and where I saved
a lot of the data last night using Knoppix (although I ran into an issue
with "splicing" files that I need to resolve.

In addition, for the bricked operating system, I have an appointment at the
Microsoft Genius Bar over at the Westfield Mall in the middle of Silicon
Valley on Stevenscreek Blvd in Santa Clara (+1-408-454-5940) who have hours
from midnight to midnight so it's easy to make an appointment with them.

The good news, on topic for rec.photo.digital, is that I have been
transferring photos from the phone of the repair process over to the newly
installed Windows 10 Pro PC without any issues, either via WiFi pver the
LAN, Bluetooth over ad-hoc services, or over USB cable (it just works).
http://wetakepic.com/images/2018/02/24/6xt104k.jpg

Apologies, I didn't read that you'd gone through all of that. Good luck.

  #18  
Old February 25th 18, 03:58 AM posted to rec.photo.digital,alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default A simple way to transfer photos from your phone to Windows withoutinstalling anything on either

ultred ragnusen wrote:
Paul wrote:

Once I burn the ISO to a disk will it be 'bootable' or will additional
action be required first?

It requires dancing a jig on one foot.


The Tier 2 Microsoft support person at +1-800-642-7676 took control of
another Windows 10 Pro system to download, burn, test, and run the same
sequence of repair that we ran (and failed at) using the bricked Windows 10
Pro recovery console.
http://wetakepic.com/images/2018/02/...dvd_repair.jpg

For the data, Knoppix worked just fine, but I am getting a very common
error from Knoppix on files that shouldn't have that error, where, when I
google for the error, NONE of the common causes can possibly be why I'm
getting that error.
Error splicing file: Value too large for defined data type.
http://wetakepic.com/images/2018/02/...x_error_01.jpg

The odd thing is that /all/ the root causes of that common error on the net
don't apply here, because the Knoppix boot alone exhibits the problem when
I copy the file to /tmp staying completely within the Knoppix file system
for the destination file.
http://wetakepic.com/images/2018/02/...x_error_02.jpg

On the net, the common reasons for that common error don't apply:
- It doesn't seem to be an NTFS issue since all the HDDs are NTFS
- It has nothing to do with the 4GB limit on file size

When Windows is installed on more than a 100 million machines, would
distributing a broken image work ? How many people would ever
figure it out ?


The second tier Microsoft support tech told me it's pretty common, saying
the reasons are many.
1. It could be a driver conflict
2. It could be a setup conflict
3. It could be a CPU conflict (the AMD CPUs were harder hit than Intel)
4. It could be a corrupted HDD (which is always a possibility)
5. It could be that I customized something that Microsoft didn't like
etc.

The Microsoft Genius Bar personnel (or whatever they're called) should be
able to allow me to tell you more when I go to my appointment.

If 100 million people phone the Microsoft support line with
"help me convert the ISO I downloaded into something useful",
how many Tier 0 employees do you think that's going to take
to help them out ? The telephone switch board will be absolutely jammed
for months and months.


I have to admit they spent at least an hour downloading, installing, and
activating Microsoft Office 2007 Pro yesterday, and a different tech spent
at least three hours trying to repair my bricked system. They will likely
spend a few more hours at the Microsoft Genius Bar (or whatever it's
called), where they'll have access to all the information in the support
ticket that has been filed to determine what the bug is due to.

I'll let you know more when I know more, but the net is that Knoppix was
the first data-recovery system I've tried, as per your suggestion to back
up the data BEFORE going to the Microsoft Genius Bar (or whatever it's
called). I'll try the other methods, where I'm confident that the data will
be recovered since there's nothing wrong with the hard disk drive as far as
I can tell.

http://wetakepic.com/images/2018/02/24/boot_device.jpg


I had another think about this, and the first question I've
got is

What utility is this ? "Finished" box.

http://wetakepic.com/images/2018/02/...x_error_01.jpg

I tried to match that dialog with some searches but was not
successful. Since Google has ruined some of their search tools
in the name of the Getty legal challenge, I can't even enter a
snip of the orange triangle and try to get a match on that.

I see a dialog box with the word "Finished" but I can't tell what
utility put that dialog box there.

I'm beginning to think you're running a scavenger, one that scans
through the disk for recognizable file headers and tries to
reconstruct files. Such tools, will produce a hundred thousand
useless unnamed fragments of files, if given a chance.
(I know, because I tried going through a folder of such
fragments once, and it was a total waste of time.)

So maybe before I jump to conclusions inappropriate for the
situation, I need some context, like what utility did that.

I don't think the "splicing" error is that bogus error based
on fstat or fstat64, and instead, it's a utility that does
actual splicing. Such utilities locate clusters of fragmented
files, they somehow conclude the disparate clusters belong
together and slap them together.

When you use "undelete" utilities (i.e. what you shouldn't
be using in this case), those take advantage of the fact the
slot for a file, only has one byte flipped indicating the
file is deleted. This leaves lots of information for reconstruction.
Including info about what clusters are used for the file. If the
(old, deleted) file does not "collide" with any new usage of the
disk resources, the undelete utility gives a "good" status for the
file, meaning "if I recover it for you, the file will be complete".
And that status is possible, because of the nature of the situation.

However, if the $MFT is lost, scanning through a fragmented disk
trying to do stuff based purely on file headers, is doomed from the
start. And that's a kind of scavenger behavior (i.e. not an undelete
utility). Can it take advantage of the $MFT ? It could certainly try.
That's if it can find the $MFT.

So maybe by context, it can tell there are too many clusters, or
the file it's reconstructing no longer makes sense (the series
of 4CC codes doesn't look right). Maybe a file type has a length
parameter, and the length parameter doesn't match the number
of clusters being spliced to rebuild the file.

Paul
  #19  
Old February 25th 18, 05:43 AM posted to rec.photo.digital,alt.windows7.general
nospam
external usenet poster
 
Posts: 4,718
Default A simple way to transfer photos from your phone to Windows without installing anything on either

In article , Paul
wrote:

I'm beginning to think you're running a scavenger, one that scans
through the disk for recognizable file headers and tries to
reconstruct files. Such tools, will produce a hundred thousand
useless unnamed fragments of files, if given a chance.
(I know, because I tried going through a folder of such
fragments once, and it was a total waste of time.)


maybe the tools you used didn't work well. the better tools not only
find the names, but also the file/folder hierarchy, and can reconstruct
as much as it can.
  #20  
Old February 27th 18, 04:03 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

Paul wrote:

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.
http://torrent.unix-ag.uni-kl.de:6969/

Since you say you're staying "on-platform" and not using
SAMBA/CIFS for this transfer, the result is highly
unusual.


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..
http://wetakepic.com/images/2018/02/...a_cables_1.jpg

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.
http://wetakepic.com/images/2018/02/...ystem8f091.jpg

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
(memtest86+).


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.
http://wetakepic.com/images/2018/02/...il_store_1.jpg

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.
  #21  
Old February 27th 18, 04:17 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

Paul wrote:

I had another think about this, and the first question I've
got is

What utility is this ? "Finished" box.

http://wetakepic.com/images/2018/02/...x_error_01.jpg


Oh. That. It's simply the dialog that Knoppix gives you when you select a
directory to right click and "copy" and then you select a location to right
click and "paste".

Anyway, I picked up the machine from the Microsoft Store today where they
found nothing wrong with the HDD or memory, but they couldn't recover the
operating system. I asked them what they ran and they spit off a bunch of
words (fixboot, scanos, chkdsk, diskpart) but mostly they said they used
"bcdedit" after running full diagnostics on the HDD and RAM and
motherboard.
http://wetakepic.com/images/2018/02/...il_store_2.jpg

I see a dialog box with the word "Finished" but I can't tell what
utility put that dialog box there.


It's just the normal copy and paste of Knoppix.
But it's all over. The Microsoft Update bricked OS is a goner because I
tried both Microsoft telephone support and the retail store in the middle
of Silicon Valley (right across from the Apple store).
http://wetakepic.com/images/2018/02/...il_store_3.jpg

The bricked MS Windows 10 update is just a disk drive now.
Windows seems to mount it just fine once I bought a SATA III cable and a
molex-to-SATA connector to hook it up as a second HDD.
http://wetakepic.com/images/2018/02/...e_system_2.jpg
(BTW, I have no idea what that 100GB "system reserved" partition is as I
didn't make it to my knowledge.)
  #22  
Old February 27th 18, 04:27 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

nospam wrote:

maybe the tools you used didn't work well. the better tools not only
find the names, but also the file/folder hierarchy, and can reconstruct
as much as it can.


The whole saga is over and done with since Microsoft can't recover the
operating system they, themselves, bricked, and where two different
Microsoft Retail store employees told me this is very common, where they
get a system bricked by the Windows 10 update at least once a day.

Interestingly, the Microsoft retail store in the middle of Silicon Valley
is directly across the aisle from the Apple Sto
http://wetakepic.com/images/2018/02/...il_store_1.jpg

The Microsoft store is almost a direct copy of the Apple model, as far as I
can tell, only about twice the size.
http://wetakepic.com/images/2018/02/...il_store_5.jpg

But, in both cases, I've never had any success bringing anything to either
the Microsoft or Apple "genius" employees, who seem to know far less than
you guys do (because they always fail - and I only bring the hard problems
to them because that's when I failed too).
http://wetakepic.com/images/2018/02/...il_store_1.jpg

PS: The Microsoft Store feeds you though, while the Apple store does not.

  #23  
Old February 27th 18, 04:46 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

Mike S wrote:

Apologies, I didn't read that you'd gone through all of that. Good luck.


No problem. I appreciate the help, and the tribal record will show others
how to recover from a bricked MS Windows 10 Pro update.

Basically, you must first try all the viable options in the Windows
recovery console using the original HDD.
http://wetakepic.com/images/2018/02/...tore_gui_1.jpg

Then you do all that again, using the absolute latest DVD ISO you can find,
and, if you can find the same DVD ISO as the OS that was bricked, you do it
a third time.
http://wetakepic.com/images/2018/02/...dvd_repair.jpg

That's all that the Microsoft Technical Support people will do, so then you
bring it down to the local Microsoft Retail Store for them to try to fix.
http://wetakepic.com/images/2018/02/...il_store_6.jpg

You leave it with them for a few days, where they will try to recover the
OS but if they can't they'll be glad to recover your data (which I didn't
have them do because I backed it up with Knoppix ahead of time).
http://wetakepic.com/images/2018/02/...il_store_7.jpg

They will back up your data to their servers or to any drive you give them,
if you want them to, but I can't imagine that they could /find/ your data,
so I'm sure if you trust them, you'll lose a lot.
http://wetakepic.com/images/2018/02/...il_store_1.jpg

Anyway, they will fail but when I asked them what they did, they told me
they first ran diagnostics, then they tried the recovery console of the
boot drive, then the recovery console of the latest Windows Creator
edition, and then the recovery console of an older version of Windows 10
and then they ran bcdedit to try to fix the boot record.

It all failed but they said there's nothing wrong with the HDD or RAM or
motherboard so I picked up my desktop today and am using it now after
stopping off at Fryes to buy an SATA III cable and a molex-to-SATA adapter
for the power.
http://wetakepic.com/images/2018/02/...a_cables_1.jpg

I had to simply move the SATA position 1 on the motherboard to the boot
drive, leaving SATA 2 on the motherboard connected to the DVD disc drive,
and then put the new SATAIII cable on SATA position 3 on the motherboard to
mount the old HDD, and everything booted up fine.
http://wetakepic.com/images/2018/02/...e_system_2.jpg

I can "see" the old HDD, plus some debugging files the Microsoft store
geniuses left behind.
http://wetakepic.com/images/2018/02/...ystem8f091.jpg

Where the issue is really closed except for me to try to write up the saga
so that the Windows tribal knowledge is updated with the lessons learned.

Basically, some of the lessons learned is:
1. Windows 10 Update bricks a lot of systems (at least one a day is handled
by the Microsoft retail store)
2. The solution first is to try every viable option in the recovery
console, and then try it with a new Windows 10 ISO and then with an old
Windows 10 ISO.
3. If that fails, then try to recover the boot records with bcdedit.

When/if that fails, you simply start over after backing up your data, where
you "should" be able to mount the HDD (I was able to) to save your data
with testdisk or knoppix or ddrescue or PhotoRec or Recuva, etc.
http://wetakepic.com/images/2018/02/...t_device_1.jpg

In my case, it mounted just fine - although Knoppix gave some weird errors
but I'm not too worried because after buying SATA and power cables, I now
have two terabyte HDDs in my laptop.
http://wetakepic.com/images/2018/02/...t_device_2.jpg
  #24  
Old February 27th 18, 04:58 AM posted to rec.photo.digital,alt.windows7.general
nospam
external usenet poster
 
Posts: 4,718
Default A simple way to transfer photos from your phone to Windows without installing anything on either

In article , ultred ragnusen
wrote:

The whole saga is over and done with since Microsoft can't recover the
operating system they, themselves, bricked, and where two different
Microsoft Retail store employees told me this is very common, where they
get a system bricked by the Windows 10 update at least once a day.


big deal. there more than half a billion win10 users. once a day per
store is nothing.

Interestingly, the Microsoft retail store in the middle of Silicon Valley
is directly across the aisle from the Apple Sto


the microsoft stores are almost always near apple stores, except
they're a *lot* less crowded, often with the only people in them being
staff.

The Microsoft store is almost a direct copy of the Apple model,


yep. everyone copies apple.

as far as I
can tell, only about twice the size.


that depends on the store. some apple stores are *huge* and the older
smaller ones are being expanded or relocated.



PS: The Microsoft Store feeds you though, while the Apple store does not.


i've never seen food offered in any microsoft store.
  #25  
Old February 27th 18, 05:18 AM posted to rec.photo.digital,alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default A simple way to transfer photos from your phone to Windows withoutinstalling anything on either

ultred ragnusen wrote:
Paul wrote:

I had another think about this, and the first question I've
got is

What utility is this ? "Finished" box.

http://wetakepic.com/images/2018/02/...x_error_01.jpg


Oh. That. It's simply the dialog that Knoppix gives you when you select a
directory to right click and "copy" and then you select a location to right
click and "paste".

Anyway, I picked up the machine from the Microsoft Store today where they
found nothing wrong with the HDD or memory, but they couldn't recover the
operating system. I asked them what they ran and they spit off a bunch of
words (fixboot, scanos, chkdsk, diskpart) but mostly they said they used
"bcdedit" after running full diagnostics on the HDD and RAM and
motherboard.
http://wetakepic.com/images/2018/02/...il_store_2.jpg

I see a dialog box with the word "Finished" but I can't tell what
utility put that dialog box there.


It's just the normal copy and paste of Knoppix.
But it's all over. The Microsoft Update bricked OS is a goner because I
tried both Microsoft telephone support and the retail store in the middle
of Silicon Valley (right across from the Apple store).
http://wetakepic.com/images/2018/02/...il_store_3.jpg

The bricked MS Windows 10 update is just a disk drive now.
Windows seems to mount it just fine once I bought a SATA III cable and a
molex-to-SATA connector to hook it up as a second HDD.
http://wetakepic.com/images/2018/02/...e_system_2.jpg
(BTW, I have no idea what that 100GB "system reserved" partition is as I
didn't make it to my knowledge.)


System Reserved can be several different sizes.

If it's small like your 100MB example, you may find \BOOT
in there as well as \BOOT\BCD. If that was the case, the "Active"
or 0x80 Boot flag would also be set on that partition. The
MBR code would be looking to that partition, for the boot
manager. The BCD is the binary file with boot settings
in it.

You can look in there with your TestDisk.

Linux can be a nuisance at times, and deny access, so
sometimes it takes more work than you might have expected.
I might have had trouble with a 0x17 partition type (Hidden
NTFS) and needed to change it to 0x07 (using sudo fdisk)
and then needed to reboot. It helps to have your LiveCD
on a USB stick, for days like that :-)

If you do find your /BOOT in there, it's possible
to move it to the main C: partition. It's kept separate
like that for BitLocker users. The idea being, you can
encrypt the entire C: drive, and leave System Reserved
visible. And that's how the OS can boot. If you insist
on moving the contents of System Reserved onto C: ,
then your config is no longer "BitLocker Ready".

http://www.terabyteunlimited.com/kb/article.php?id=409

I think the BitLocker on Windows 7 uses the Elephant
Diffuser and it was removed from Windows 10. If encryption
had "belt and suspenders" the Windows 10 version is just
"belt". They removed the suspenders.

Paul
  #26  
Old February 27th 18, 05:22 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

Paul wrote:

Anyway, I'm sure you'll figure out something.


Hi Paul,

I picked up the desktop today from the Microsoft Retail Store.
http://wetakepic.com/images/2018/02/...il_store_1.jpg

On my way home, I stopped off at Fryes, to pick up the two cables needed to
attach the second HDD, which was a red SATA III cable and a molex to SATA
flat cable.
http://wetakepic.com/images/2018/02/...a_cables_1.jpg

Putting the new HDD in the SATA1 slot of the motherboard, I can boot off of
the new drive which has the latest Windows 10 Pro ISO installed.
http://wetakepic.com/images/2018/02/...t_device_2.jpg

Now that it's confirmed by the Microsoft Retail Store that the operating
system the Windows 10 update bricked is a goner, there's really nothing
left to do but back up the data and then format the disk as a new disk.
http://wetakepic.com/images/2018/02/...ystem8f091.jpg

I don't need two terabytes, where I never even needed one terabyte, so, I
guess I'm going to learn how to RAID these things.
  #27  
Old February 27th 18, 07:15 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

nospam wrote:

then don't use a system that uses bios, a system that doesn't have such
a ridiculous limitation.


Just for the record, when the Microsoft Retail Store gave me back
my PC today...
http://wetakepic.com/images/2018/02/...il_store_1.jpg

I asked what they used, and the genius guy kept talking about bcdedit
(and they left a bcdedit backup binary file on the bricked HDD).
http://wetakepic.com/images/2018/02/...ystem8f091.jpg

Here's the command options for bcdedit...

bcdedit /?

BCDEDIT - Boot Configuration Data Store Editor

The Bcdedit.exe command-line tool modifies the boot configuration data store.
The boot configuration data store contains boot configuration parameters and
controls how the operating system is booted. These parameters were previously
in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile
RAM entries (in Extensible Firmware Interface-based operating systems). You can
use Bcdedit.exe to add, delete, edit, and append entries in the boot
configuration data store.

For detailed command and option information, type bcdedit.exe /? command. For
example, to display detailed information about the /createstore command, type:

bcdedit.exe /? /createstore

For an alphabetical list of topics in this help file, run "bcdedit /? TOPICS".

Commands that operate on a store
================================
/store Used to specify a BCD store other than the current system default.
/createstore Creates a new and empty boot configuration data store.
/export Exports the contents of the system store to a file. This file
can be used later to restore the state of the system store.
/import Restores the state of the system store using a backup file
created with the /export command.
/sysstore Sets the system store device (only affects EFI systems, does
not persist across reboots, and is only used in cases where
the system store device is ambiguous).

Commands that operate on entries in a store
===========================================
/copy Makes copies of entries in the store.
/create Creates new entries in the store.
/delete Deletes entries from the store.
/mirror Creates mirror of entries in the store.

Run bcdedit /? ID for information about identifiers used by these commands.

Commands that operate on entry options
======================================
/deletevalue Deletes entry options from the store.
/set Sets entry option values in the store.

Run bcdedit /? TYPES for a list of datatypes used by these commands.
Run bcdedit /? FORMATS for a list of valid data formats.

Commands that control output
============================
/enum Lists entries in the store.
/v Command-line option that displays entry identifiers in full,
rather than using names for well-known identifiers.
Use /v by itself as a command to display entry identifiers
in full for the ACTIVE type.

Running "bcdedit" by itself is equivalent to running "bcdedit /enum ACTIVE".

Commands that control the boot manager
======================================
/bootsequence Sets the one-time boot sequence for the boot manager.
/default Sets the default entry that the boot manager will use.
/displayorder Sets the order in which the boot manager displays the
multiboot menu.
/timeout Sets the boot manager time-out value.
/toolsdisplayorder Sets the order in which the boot manager displays
the tools menu.

Commands that control Emergency Management Services for a boot application
================================================== ========================
/bootems Enables or disables Emergency Management Services
for a boot application.
/ems Enables or disables Emergency Management Services for an
operating system entry.
/emssettings Sets the global Emergency Management Services parameters.

Command that control debugging
==============================
/bootdebug Enables or disables boot debugging for a boot application.
/dbgsettings Sets the global debugger parameters.
/debug Enables or disables kernel debugging for an operating system
entry.
/hypervisorsettings Sets the hypervisor parameters.

Command that control remote event logging
=========================================
/eventsettings Sets the global remote event logging parameters.
/event Enables or disables remote event logging for an operating
system entry.
  #28  
Old February 27th 18, 07:30 AM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 248
Default A simple way to transfer photos from your phone to Windows without installing anything on either

nospam wrote:

The whole saga is over and done with since Microsoft can't recover the
operating system they, themselves, bricked, and where two different
Microsoft Retail store employees told me this is very common, where they
get a system bricked by the Windows 10 update at least once a day.


big deal. there more than half a billion win10 users. once a day per
store is nothing.


You talk like the developers I used to work with long ago, where they
figured bugs were just something that you have to learn to live with.

It's a big deal when a mandatory Microsoft Windows 10 Pro update bricks the
system. It's due to poor coding. Very poor coding. Lousy testing too.

Interestingly, the Microsoft retail store in the middle of Silicon Valley
is directly across the aisle from the Apple Sto


the microsoft stores are almost always near apple stores, except
they're a *lot* less crowded, often with the only people in them being
staff.


Interestingly, when I dropped off my computer at the Microsoft Store
earlier this week for them to fail at unbricking the operating system, I
snapped a few pictures within seconds of each other of the two stores,
which are directly across the hall from each other in Santa Clara
California.

Microsoft:
http://wetakepic.com/images/2018/02/...l_store_10.jpg
http://wetakepic.com/images/2018/02/...il_store_8.jpg
http://wetakepic.com/images/2018/02/...il_store_6.jpg

Apple:
http://wetakepic.com/images/2018/02/...il_store_1.jpg
http://wetakepic.com/images/2018/02/...il_store_2.jpg
http://wetakepic.com/images/2018/02/...il_store_3.jpg


The Microsoft store is almost a direct copy of the Apple model,


yep. everyone copies apple.


The Santa Clara California Microsoft Store was a lot bigger than the Apple
store though, and there was a LOT of gaming going on, with kids everywhere
playing the Xbox for free and a special glass room just for seminars.
http://wetakepic.com/images/2018/02/...il_store_5.jpg

But it did seem like a bigger copy of Apple, so I agree that they
capitalized on what Apple came up with (even though they told me they've
been there for many years).


as far as I
can tell, only about twice the size.


that depends on the store. some apple stores are *huge* and the older
smaller ones are being expanded or relocated.


This is the one in Santa Clara California, where the Microsoft Store is
clearly huge compared to the Apple Store.

PS: The Microsoft Store feeds you though, while the Apple store does not.


i've never seen food offered in any microsoft store.


They offered me a the coke you see in this picture...
http://wetakepic.com/images/2018/02/...il_store_2.jpg
  #29  
Old February 27th 18, 08:16 AM posted to rec.photo.digital,alt.windows7.general
nospam
external usenet poster
 
Posts: 4,718
Default A simple way to transfer photos from your phone to Windows without installing anything on either

In article , ultred
ragnusen wrote:


The whole saga is over and done with since Microsoft can't recover the
operating system they, themselves, bricked, and where two different
Microsoft Retail store employees told me this is very common, where they
get a system bricked by the Windows 10 update at least once a day.


big deal. there more than half a billion win10 users. once a day per
store is nothing.


You talk like the developers I used to work with long ago, where they
figured bugs were just something that you have to learn to live with.


all software has bugs.

the reality is that win10 bricking is extremely rare and in your case,
it's almost certainly due to something you did rather than microsoft's
error.

It's a big deal when a mandatory Microsoft Windows 10 Pro update bricks the
system. It's due to poor coding. Very poor coding. Lousy testing too.


you have no idea what the cause is, nor do the 'geniuses' at the
microsoft store.

but to re-use your usual (ignorant) line, microsoft obviously doesn't
test their software in the real world.


Interestingly, the Microsoft retail store in the middle of Silicon Valley
is directly across the aisle from the Apple Sto


the microsoft stores are almost always near apple stores, except
they're a *lot* less crowded, often with the only people in them being
staff.


Interestingly, when I dropped off my computer at the Microsoft Store
earlier this week for them to fail at unbricking the operating system, I
snapped a few pictures within seconds of each other of the two stores,
which are directly across the hall from each other in Santa Clara
California.


your pictures prove my point.



as far as I
can tell, only about twice the size.


that depends on the store. some apple stores are *huge* and the older
smaller ones are being expanded or relocated.


This is the one in Santa Clara California, where the Microsoft Store is
clearly huge compared to the Apple Store.


invalid sample size.

the union square san francisco apple store was *huge*, much bigger than
any mall store. i haven't been to the new one yet, but it's reportedly
bigger.

there are even bigger apple stores than those.
  #30  
Old February 27th 18, 09:07 AM posted to rec.photo.digital,alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default A simple way to transfer photos from your phone to Windows withoutinstalling anything on either

nospam wrote:
In article , ultred
ragnusen wrote:

The whole saga is over and done with since Microsoft can't recover the
operating system they, themselves, bricked, and where two different
Microsoft Retail store employees told me this is very common, where they
get a system bricked by the Windows 10 update at least once a day.
big deal. there more than half a billion win10 users. once a day per
store is nothing.

You talk like the developers I used to work with long ago, where they
figured bugs were just something that you have to learn to live with.


all software has bugs.

the reality is that win10 bricking is extremely rare and in your case,
it's almost certainly due to something you did rather than microsoft's
error.


One of the recent issues (in 2018), was the refusal
to boot of older AMD processor based systems. This isn't
true bricking (ruining of file system), but it did prevent
people from using their computers. The user "Cameo" in the
group had an AMD system suffer that fate, and Cameo
figured out the necessary DISM command to reverse it
and got the system running again.

It's unclear exactly what kind of blooper hit Ultred's
machine, as the symptoms don't seem to match anything
I could find. A little offline DISM or SFC should have
repaired the OS base, assuming that the file system
really wasn't trashed.

My Windows 10 Insider about a week ago (I have two OSes
running Insider), both of them suffered Voumme Bitmap
trouble, as well as a series of Extended Attributes issues.
And Microsoft has been screwing around with Extended Attributes,
so it's not exactly a random occurrence. I was able to fix that,
and I was initially concerned I'd have to reinstall. But CHKDSK
came through.

The Win10 16299 is also making "bad" NTFS partitions now.
The $MFTMIRR is wrong. If you're making NTFS partitions while
running the latest version of Windows 10, I recommend going back
to Windows 7 and doing your partitioning there instead. I've had
to repair a number of $MFTMIRR entries on NTFS volumes.

It's funny that the level of "innocent" "tee hee hee" errors
is going up, at a time when we're so far along in Windows 10
development. I just can't figure out what these people
are smoking. It's worse than the webcam fiasco (where they
added a busted implementation of FrameServe to webcams,
and my webcam wouldn't work for three months). Even a chimpanzee
with one hand tied behind his back, could have backed out those
changes, apologized and fixed my webcam in a week or two, tops.
Instead, it was full speed ahead and "screw you" if you need
that webcam. "Software as a service". Um, OK. Gotcha.

Paul
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 11:37 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.