On Mon, 03 Apr 2017 10:18:57 -0400, Paul <nos...@needed.invalid>
wrote:
>Micky wrote:
>> I'm trying to install Kindle for PC on my XP laptop. Do any of you
>> have that? What happens is first it downloads a bunch of files and
>> when it reaches 100%, then it says "Please wait while setup is
>> loading. ... unpacking data" and a little while after that reaches
>> 100%, there is a blink on the screen which is the install spash
>> screen. It's gone in less than a 20th of a second and that's the end
>> of the whole process.
>>
>> One time it got slow in the middle I guess and it was a very pretty,
>> colorful, darkish little window. This time it was a bigger grey
>> window with a progress bar with just a little green in it at the
>> start, and then it closed before I could look at the rest.
>>
>> One time I had Everywhere running and showing all the files on the
>> laptop, sorted by date, so any new files would show up (and indeed
>> they did. New Firefox profile files kept showing up minutes after I'd
>> done anything with FF.) but even when it was expanding the files, no
>> new files appeared on the Everywhere screen. How can that be?
>>
>> Any suggestions?
>
>If files are not stored on a storage device, they can
>always be kept in RAM somewhere. I've seen one installer
>"hide" in some way like that, while I was unpacking
>it in WINE.
That makes sense. Especially since this netbook has only 1 gig of
RAM. I already tried to install the program first thing, before
starting other programs, when I'd have as much RAM etc. as possible
available. I don't know what "etc." refers to but I didn't try to
fully form my reasons for my plan; I just followed procedure.
I'll try harder next time to have even less running. I'll use Task
Manager to stop everything I don't think matters.
But before that, it occurred to me that if they're going to unpack to
RAM, then surely they gave an option to unpack to the HDD, for people
like me, for debugging, etc.
So I opened a cmd window and ran the install program with /? hoping
it would explain options, but it ignored /? and ran as normal,
blinking to an end as usual. Is there, perhaps, a standard
option/switch to get a program to use/unpack to HDD files instead of
RAM that I could try.
If worst comes to worst, I'll wait until I get home, where my 4GB box
is scheduled to go up to 8GB, but this one kindle book I'm trying to
read does relate somewhat to my travels, so I was trying to read it
before I went home.
>The average installer doesn't go to that
>much trouble, and unpacks in a TEMP somewhere.
>
>Generally, such techniques are not favored, because of
>the danger the user could be on a low-RAM system.
Exactly.
>For example, you could set up a Win10 Virtual Machine,
>dial down the RAM setting to 256MB, then run the Kindle
>installer... and see what happens :-)
Some day I will have to try the VM thing. Haven't done it yet.