A Photography forum. PhotoBanter.com

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 » PhotoBanter.com forum » Digital Photography » Digital Photography
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 Display Modes
  #41  
Old February 27th 18, 04:46 PM posted to rec.photo.digital,alt.windows7.general
nospam
external usenet poster
 
Posts: 24,165
Default A simple way to transfer photos from your phone to Windows without installing anything on either

In article , Paul
wrote:

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.


that one was rushed, and once they realized it was causing problems, it
was pulled.
  #42  
Old February 27th 18, 07:35 PM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 92
Default A simple way to transfer photos from your phone to Windows without installing anything on either

Paul wrote:

"Software as a service". Um, OK. Gotcha.


I'm not quite sure exactly what happened, but I think this was the
sequence.

1. I had Windows 10 Pro set up to never update.
2. Windows 10 Pro was just fine, stuck at Version 1511 OS Build 10586.1106
3. All subsequent updates failed, but automatically backed themselves out
4. The 16299 Upgrade from Nov 2017 failed in Jan, but didn't back itself
out

Anyway, the hard drive and memory were checked out by Microsoft so there's
nothing wrong but the bricked operating system, which is no big deal since
I've bought a new terabyte disk, and now have two terabyte disks side by
side (which I might RAID once I clean them out - but I never did RAID
before and googling finds that there are a LOT of up-front decisions to
make).
  #43  
Old February 27th 18, 07:39 PM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 92
Default A simple way to transfer photos from your phone to Windows without installing anything on either

nospam wrote:

more than likely, it was a significant factor that
caused your bricking.


I checked my records on the old HDD now that it's mounted to Windows, where
it was stable at "Windows 10 Pro Version 1511 OS Build 10586.1106" for
years.

So I was able to do the impossible, for a while, which is stave off the
Windows 10 Pro updates.

I suspect Microsoft never coded the if-then-else to handle jumping from
Windows 10 Pro Version 1511 OS Build 10586.1106 to the 16299 Upgrade from
November 2017 (1709 release).

It's a bug on their part, almost certainly, since I only flipped the
switches that they provided.
  #44  
Old February 27th 18, 07:49 PM posted to rec.photo.digital,alt.windows7.general
nospam
external usenet poster
 
Posts: 24,165
Default A simple way to transfer photos from your phone to Windows without installing anything on either

In article , ultred
ragnusen wrote:


more than likely, it was a significant factor that
caused your bricking.


I checked my records on the old HDD now that it's mounted to Windows, where
it was stable at "Windows 10 Pro Version 1511 OS Build 10586.1106" for
years.

So I was able to do the impossible, for a while, which is stave off the
Windows 10 Pro updates.


that's a very, very stupid thing to do. you're not getting bug fixes,
security patches and new features.

I suspect Microsoft never coded the if-then-else to handle jumping from
Windows 10 Pro Version 1511 OS Build 10586.1106 to the 16299 Upgrade from
November 2017 (1709 release).


since just about nobody is in that situation, there's very little
reason to bother.

there are far more important problems to address, ones that affect many
more people.

you're using win10 *not* in the way it was designed to be used and will
end up with problems.

tl;dr user error.
  #45  
Old February 27th 18, 08:24 PM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 92
Default A simple way to transfer photos from your phone to Windows without installing anything on either

nospam wrote:

So I was able to do the impossible, for a while, which is stave off the
Windows 10 Pro updates.


that's a very, very stupid thing to do. you're not getting bug fixes,
security patches and new features.


The answer to that objection is that if I had wanted Microsoft updates, I
would have loaded them on my own.

Just like I do with my iPads to prevent the diarrhea that is iOS constant
updates of buggy releases (that even, as you know, Craig Federighi at Apple
admitted earlier this month) I don't want to load any operating system
update unless I know I want or need something on that operating system
update.

And that almost never happens.

Of my iPads, for example, they are still on 9.x and 10.x as I recall, and
they work just fine - where I would have left them at 7.0.0 had I known the
hell I would go through with them breaking Linux connectivity with 7.0.1
since iOS isn't even tested in the real world (where Apple support merely
says the real world "isn't supported" so they don't care what they break
outside the walled garden).

I do the same with Android, with all Google framework and Google Play
updates turned off - and that works just fine for me since I'll update what
I want when I want.

I suspect Microsoft never coded the if-then-else to handle jumping from
Windows 10 Pro Version 1511 OS Build 10586.1106 to the 16299 Upgrade from
November 2017 (1709 release).


since just about nobody is in that situation, there's very little
reason to bother.


It's a classic coding rule to abort gracefully when the unexpected occurs,
which Microsoft did - for years - but not recently.

there are far more important problems to address, ones that affect many
more people.


You have the tunnel mindset of the classic Silicon Valley coder, where I
know hundreds of them, perhaps thousands. You have no concept of how to
code properly to handle exceptions if you actually believe that.

you're using win10 *not* in the way it was designed to be used and will
end up with problems.


I flip the switches that Microsoft provides - so it's a bug if they can't
handle their own switches being flipped.

Nonetheless, after having been burned, I'm going to flip fewer switches
this time. Microsoft and Apple and Google and Ubuntu all have a way of
enforcing their rules, all of which I customize probably far more than does
the average person so I likely run into a lot more bugs than the average
person does.
  #46  
Old February 27th 18, 09:18 PM posted to rec.photo.digital,alt.windows7.general
Davoud
external usenet poster
 
Posts: 639
Default A simple way to transfer photos from your phone to Windows without installing anything on either

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


Yeah, but the Apple Store sells stuff that "just works," while the
Microsoft Store does not

--
I agree with almost everything that you have said and almost everything that
you will say in your entire life.

usenet *at* davidillig dawt cawm
  #47  
Old February 27th 18, 09:26 PM posted to rec.photo.digital,alt.windows7.general
nospam
external usenet poster
 
Posts: 24,165
Default A simple way to transfer photos from your phone to Windows without installing anything on either

In article , ultred ragnusen
wrote:


So I was able to do the impossible, for a while, which is stave off the
Windows 10 Pro updates.


that's a very, very stupid thing to do. you're not getting bug fixes,
security patches and new features.


The answer to that objection is that if I had wanted Microsoft updates, I
would have loaded them on my own.


that's not an answer. it's an excuse for foolishness.

Just like I do with my iPads to prevent the diarrhea


moving goalposts to trolling.



I suspect Microsoft never coded the if-then-else to handle jumping from
Windows 10 Pro Version 1511 OS Build 10586.1106 to the 16299 Upgrade from
November 2017 (1709 release).


since just about nobody is in that situation, there's very little
reason to bother.


It's a classic coding rule to abort gracefully when the unexpected occurs,
which Microsoft did - for years - but not recently.


there's no way to cover every possible situation.

rare ones, particularly ones that are the result of users going out of
their way to break things, are not a high priority.

in fact, they're best ignored. anyone circumventing the normal update
process should know the risks they're taking and be able to deal with
the inevitable problems that will occur.


there are far more important problems to address, ones that affect many
more people.


You have the tunnel mindset of the classic Silicon Valley coder, where I
know hundreds of them, perhaps thousands. You have no concept of how to
code properly to handle exceptions if you actually believe that.


ad hominem.
  #48  
Old February 27th 18, 11:04 PM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 92
Default A simple way to transfer photos from your phone to Windows without installing anything on either

nospam wrote:

The answer to that objection is that if I had wanted Microsoft updates, I
would have loaded them on my own.


that's not an answer. it's an excuse for foolishness.


If I had wanted Microsoft updates, I would have downloaded them.
It's really that simple.

Just like I do with my iPads to prevent the diarrhea


moving goalposts to trolling.


The point is that there is generally nothing in the newer releases of any
mature operating system, whether it be Linux, Windows, iOS, or Android,
that I care about and that is worth the huge risk, especially with Apple
products which are not tested outside the walled garden, which you're very
well aware of.

It's a classic coding rule to abort gracefully when the unexpected occurs,
which Microsoft did - for years - but not recently.


there's no way to cover every possible situation.


Of course there is. If the answer isn't the expected answer, then you abort
gracefully.

rare ones, particularly ones that are the result of users going out of
their way to break things, are not a high priority.


If Microsoft provides a switch, they should test their software with those
switches thrown.

The poor coding reminds me of Windows iTunes, which will go where you ask
it to go but all the ancillary program bloat that comes along with iTunes
doesn't follow any good coding practices, hence they don't anywhere near
where you told iTunes to go.

in fact, they're best ignored. anyone circumventing the normal update
process should know the risks they're taking and be able to deal with
the inevitable problems that will occur.


In this case, the answer is clear for the tribal knowledge record:
a. If Microsoft Windows Update bricks your system, then
b. First try to recover using all the options in the recovery console
c. Then try those same options after booting to the latest release on DVD
d. Then try those same options after booting to an older release DVD
e. If they all fail, then try to fix the MBR with the BCDEDITE fixboot
f. If that still fails, then start fresh after recovering the data.

To recover the data, any of the following will work:
A. Attach the drive to an SATA/IDE/EIDE/PATA adapter to USB
B. Attach the drive to the motherboard with a SATAIII cable set
C. Access the drive after booting to Windows (either DVD or on HDD)
D. Access the drive after booting to a recovery OS (e.g., Knoppix on DVD)
E. Run any of the following programs, as desired
1. copy
2. ddrescue
3. recuva
4. testdisk
5. photrec
etc.
  #49  
Old February 27th 18, 11:08 PM posted to rec.photo.digital,alt.windows7.general
ultred ragnusen
external usenet poster
 
Posts: 92
Default A simple way to transfer photos from your phone to Windows without installing anything on either

Davoud wrote:

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


Yeah, but the Apple Store sells stuff that "just works," while the
Microsoft Store does not


Let's not go there because you're very well aware that there is zero app
functionality on iOS that isn't already on Android, and likely on Microsoft
also, while there is /tons/ and /tons/ (and /tons/) of app functionality on
Android that isn't on iOS (e.g., loading any launcher, setting up the
desktop any way you like, automatic call recording, torrenting, graphical
display of wifi signal strength for all available APs over time, accurate
reporting of cell tower information, an app drawer app, youtube
searching/downloading/playing/extraction/etc in a single youtube clone app
without ever once seeing an ad, etc.).
  #50  
Old February 28th 18, 12:16 AM posted to rec.photo.digital,alt.windows7.general
Ken Blake[_2_]
external usenet poster
 
Posts: 12
Default A simple way to transfer photos from your phone to Windows without installing anything on either

On Tue, 27 Feb 2018 10:35:09 -0800, ultred ragnusen
wrote:

I've bought a new terabyte disk, and now have two terabyte disks side by
side (which I might RAID once I clean them out - but I never did RAID
before and googling finds that there are a LOT of up-front decisions to
make).



If you mean RAID 0 (striping), although it sounds like it should speed
up disk access, my experience is that it doesn't.

If you mean RAID 1 (mirroring), be aware that it is *not* a backup
solution. RAID 1 uses two or more drives, each a duplicate of the
others, to provide redundancy, not backup. It's used in situations
(almost always within corporations, not in homes) where any downtown
can't be tolerated, because the way it works is that if one drive
fails the other takes over seamlessly.

Although some people thing of RAID 1 as a backup technique, that is
*not* what it is, since it's subject to simultaneous loss of the
original and the mirror to many of the most common dangers threatening
your data--severe power glitches, nearby lightning strikes, virus
attacks, theft of the computer, etc. Most companies that use RAID 1
also have a strong external backup plan in place.

"Why RAID is (usually) a Terrible Idea"
http://www.pugetsystems.com/articles?&id=29

 




Thread Tools
Display Modes

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 Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
After installing windows 7 codec pack NO MORE jpg Thumbnail View in Explorer? sb Digital Photography 0 May 9th 11 11:39 AM
transfer picture to phone? Jürgen Exner Digital Photography 0 May 20th 09 04:57 PM
transfer picture to phone? Savageduck[_2_] Digital Photography 1 May 20th 09 04:16 PM
Windows can't read card reader after Installing PSE 4 Rick[_4_] Digital Photography 1 October 16th 07 02:06 PM
NEF transfer from Mac OSX or OS9 to Windows XP Kit Bonin Digital Photography 3 January 6th 05 07:57 PM


All times are GMT +1. The time now is 02:57 PM.


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