Problem with Users folder

Nil wrote:

jbm wrote:

Tonight, I have just run about a hundred FLAC files successfully,
transferred the resulting wav file to the Cloud drive, and went into
the AppData\Temp folder to delete the rubbish. Except there's no
rubbish in there!!!!!!! Work that one out. Now, where did I put my
Windows XP installation disks?

I don't see any problem here. What are you complaining about?

That the cockroach disappeared when he turned on the light. He had a
problem. He tried to investigate. It disappeared. The sucker wasted
his time. When it goes dark (he isn't watching), the cockroach could
come back.

On 5/4/2017 10:29 PM, Char Jackson wrote:
On Thu, 4 May 2017 23:27:53 +0100, jbm wrote:

On 04/05/2017 14:18, Paul wrote:
Wolf K wrote:
On 2017-05-03 18:17, jbm wrote:
[...]
Secondly, I am a bit ****ed off with HP for installing such a small
drive as their main C:\ drive.
[...]

Well, they were trying to meet a price point....


These are the specs on the HP Pavilion 550-103na Desktop PC.

Hard drive: 2 TB HDD & 128 GB SSD

I don't think that's a particular egregious setup.

If having C: on an SSD is cramping your style,
you can always move the contents of the 128GB SSD
into the 2TB HDD, resize the C: partition, done.

The 128GB SSD is likely to have the recovery partition
and the like, while the 2TB hard drive should have
hardly any valuable OEM info at all on it.

So you should be able to whip up a 1800GB C:
partition, if you want one. I think I could
do that in one shot, with Macrium Reflect Free.

http://www.macrium.com/reflectfree.asp

By placing C: on the hard drive, it won't run as
fast, but it will "suit your lifestyle" better
(if you want to "store it all" on C: ). It can be
fixed.

Paul


On delivery, the 2TB D:\ drive was empty apart from its label
DATADRIVE1. Just one partition and no stored folders or files.

The 128GB drive contained the OS (Win10) on C:\, a SYSTEM drive Z:\, and
an unspecified RECOVERY drive; i.e. 3 separate partitions.

Transferring the OS C:\ drive onto the 2TB drive sounds like a good
idea. I'll have to look into that. What are the major pitfalls? There
have got to be some!!! The big question is how the hell do you create a
new C:\ drive when one already exists???

One way that's frequently recommended around here, which I agree with,
is to use Macrium Reflect Free to clone C: to D:. Do the cloning
operation, then shut down. Disconnect the SSD and boot from the 2TB
drive. Shut down, reconnect the SSD, boot from the 2TB drive, format the
SSD and use it for whatever you like. Disk performance will take a hit
by going from SSD to spinning drive, but before too long you'll stop
noticing it.

God. I loved Windows XP!

The OS doesn't matter in this case.


Using a spinning drive as your windows drive when you have a perfectly
good SSD to run it on is a real dumb Idea!
Furthermore 128 GB is plenty big enough for windows IF you don't put any
other crap on it.
I have 3 machines running Windows 10 on 128 GB SSDs and in all cases
Windows uses 27 to 32GB, lean and mean. JUST INSTALL ALL your other
stuff and data on the large spinning drive.

Rene

On 3/5/2017 6:27 AM, jbm wrote:
... user folder in C:\Users\Xxxxx\AppData\Local\Temp. (Xxxxx is my
name.) This particular folder was hidden which didn't help matters.
....
What I have just found in the Users folder are 396 .wav and .flac files
totalling 58GB. No wonder I am running out of room on a 117GB drive. If
....

How could you not know that you downloaded a 58GB file? Someone tampered
with your computers?

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa

On Fri, 5 May 2017 22:07:54 +0800, "Mr. Man-wai Chang"
wrote:

On 3/5/2017 6:27 AM, jbm wrote:
... user folder in C:\Users\Xxxxx\AppData\Local\Temp. (Xxxxx is my
name.) This particular folder was hidden which didn't help matters.
....
What I have just found in the Users folder are 396 .wav and .flac files
totalling 58GB. No wonder I am running out of room on a 117GB drive. If
....

How could you not know that you downloaded a 58GB file? Someone tampered
with your computers?

This is probably obvious to most, but "396 .wav and .flac files
totalling 58GB" is not "a 58GB file".

On Fri, 5 May 2017 08:18:22 -0500, Rene Lamontagne
wrote:

On 5/4/2017 10:29 PM, Char Jackson wrote:
On Thu, 4 May 2017 23:27:53 +0100, jbm wrote:

On 04/05/2017 14:18, Paul wrote:
Wolf K wrote:
On 2017-05-03 18:17, jbm wrote:
[...]
Secondly, I am a bit ****ed off with HP for installing such a small
drive as their main C:\ drive.
[...]

Well, they were trying to meet a price point....


These are the specs on the HP Pavilion 550-103na Desktop PC.

Hard drive: 2 TB HDD & 128 GB SSD

I don't think that's a particular egregious setup.

If having C: on an SSD is cramping your style,
you can always move the contents of the 128GB SSD
into the 2TB HDD, resize the C: partition, done.

The 128GB SSD is likely to have the recovery partition
and the like, while the 2TB hard drive should have
hardly any valuable OEM info at all on it.

So you should be able to whip up a 1800GB C:
partition, if you want one. I think I could
do that in one shot, with Macrium Reflect Free.

http://www.macrium.com/reflectfree.asp

By placing C: on the hard drive, it won't run as
fast, but it will "suit your lifestyle" better
(if you want to "store it all" on C: ). It can be
fixed.

Paul


On delivery, the 2TB D:\ drive was empty apart from its label
DATADRIVE1. Just one partition and no stored folders or files.

The 128GB drive contained the OS (Win10) on C:\, a SYSTEM drive Z:\, and
an unspecified RECOVERY drive; i.e. 3 separate partitions.

Transferring the OS C:\ drive onto the 2TB drive sounds like a good
idea. I'll have to look into that. What are the major pitfalls? There
have got to be some!!! The big question is how the hell do you create a
new C:\ drive when one already exists???

One way that's frequently recommended around here, which I agree with,
is to use Macrium Reflect Free to clone C: to D:. Do the cloning
operation, then shut down. Disconnect the SSD and boot from the 2TB
drive. Shut down, reconnect the SSD, boot from the 2TB drive, format the
SSD and use it for whatever you like. Disk performance will take a hit
by going from SSD to spinning drive, but before too long you'll stop
noticing it.

God. I loved Windows XP!

The OS doesn't matter in this case.


Using a spinning drive as your windows drive when you have a perfectly
good SSD to run it on is a real dumb Idea!

I totally agree, but the OP is apparently in a tight spot. For his
system drive, does he use a drive that's very fast and way too small, or
does he use a drive that's slow and probably way bigger than it needs to
be? Neither are good choices, IMHO.

Furthermore 128 GB is plenty big enough for windows IF you don't put any
other crap on it.
I have 3 machines running Windows 10 on 128 GB SSDs and in all cases
Windows uses 27 to 32GB, lean and mean. JUST INSTALL ALL your other
stuff and data on the large spinning drive.

Again, I agree, but your use of the word "IF" is a deal breaker for me,
and possibly for the OP. I know I'm not willing to jump through those
hoops, so IMHO the minimum size for a Windows system drive is 512GB. My
use case might not apply to anyone else, however.

On 5/7/2017 10:20 AM, Char Jackson wrote:
On Fri, 5 May 2017 08:18:22 -0500, Rene Lamontagne
wrote:

On 5/4/2017 10:29 PM, Char Jackson wrote:
On Thu, 4 May 2017 23:27:53 +0100, jbm wrote:

On 04/05/2017 14:18, Paul wrote:
Wolf K wrote:
On 2017-05-03 18:17, jbm wrote:
[...]
Secondly, I am a bit ****ed off with HP for installing such a small
drive as their main C:\ drive.
[...]

Well, they were trying to meet a price point....


These are the specs on the HP Pavilion 550-103na Desktop PC.

Hard drive: 2 TB HDD & 128 GB SSD

I don't think that's a particular egregious setup.

If having C: on an SSD is cramping your style,
you can always move the contents of the 128GB SSD
into the 2TB HDD, resize the C: partition, done.

The 128GB SSD is likely to have the recovery partition
and the like, while the 2TB hard drive should have
hardly any valuable OEM info at all on it.

So you should be able to whip up a 1800GB C:
partition, if you want one. I think I could
do that in one shot, with Macrium Reflect Free.

http://www.macrium.com/reflectfree.asp

By placing C: on the hard drive, it won't run as
fast, but it will "suit your lifestyle" better
(if you want to "store it all" on C: ). It can be
fixed.

Paul


On delivery, the 2TB D:\ drive was empty apart from its label
DATADRIVE1. Just one partition and no stored folders or files.

The 128GB drive contained the OS (Win10) on C:\, a SYSTEM drive Z:\, and
an unspecified RECOVERY drive; i.e. 3 separate partitions.

Transferring the OS C:\ drive onto the 2TB drive sounds like a good
idea. I'll have to look into that. What are the major pitfalls? There
have got to be some!!! The big question is how the hell do you create a
new C:\ drive when one already exists???

One way that's frequently recommended around here, which I agree with,
is to use Macrium Reflect Free to clone C: to D:. Do the cloning
operation, then shut down. Disconnect the SSD and boot from the 2TB
drive. Shut down, reconnect the SSD, boot from the 2TB drive, format the
SSD and use it for whatever you like. Disk performance will take a hit
by going from SSD to spinning drive, but before too long you'll stop
noticing it.

God. I loved Windows XP!

The OS doesn't matter in this case.


Using a spinning drive as your windows drive when you have a perfectly
good SSD to run it on is a real dumb Idea!

I totally agree, but the OP is apparently in a tight spot. For his
system drive, does he use a drive that's very fast and way too small, or
does he use a drive that's slow and probably way bigger than it needs to
be? Neither are good choices, IMHO.

Furthermore 128 GB is plenty big enough for windows IF you don't put any
other crap on it.
I have 3 machines running Windows 10 on 128 GB SSDs and in all cases
Windows uses 27 to 32GB, lean and mean. JUST INSTALL ALL your other
stuff and data on the large spinning drive.

Again, I agree, but your use of the word "IF" is a deal breaker for me,
and possibly for the OP. I know I'm not willing to jump through those
hoops, so IMHO the minimum size for a Windows system drive is 512GB. My
use case might not apply to anyone else, however.


If changing a few drive letters is too much of a hardship for you thats
OK by me.

Rene

On Sun, 7 May 2017 10:45:06 -0500, Rene Lamontagne
wrote:

On 5/7/2017 10:20 AM, Char Jackson wrote:
On Fri, 5 May 2017 08:18:22 -0500, Rene Lamontagne
wrote:

On 5/4/2017 10:29 PM, Char Jackson wrote:
On Thu, 4 May 2017 23:27:53 +0100, jbm wrote:

On 04/05/2017 14:18, Paul wrote:
Wolf K wrote:
On 2017-05-03 18:17, jbm wrote:
[...]
Secondly, I am a bit ****ed off with HP for installing such a small
drive as their main C:\ drive.
[...]

Well, they were trying to meet a price point....


These are the specs on the HP Pavilion 550-103na Desktop PC.

Hard drive: 2 TB HDD & 128 GB SSD

I don't think that's a particular egregious setup.

If having C: on an SSD is cramping your style,
you can always move the contents of the 128GB SSD
into the 2TB HDD, resize the C: partition, done.

The 128GB SSD is likely to have the recovery partition
and the like, while the 2TB hard drive should have
hardly any valuable OEM info at all on it.

So you should be able to whip up a 1800GB C:
partition, if you want one. I think I could
do that in one shot, with Macrium Reflect Free.

http://www.macrium.com/reflectfree.asp

By placing C: on the hard drive, it won't run as
fast, but it will "suit your lifestyle" better
(if you want to "store it all" on C: ). It can be
fixed.

Paul


On delivery, the 2TB D:\ drive was empty apart from its label
DATADRIVE1. Just one partition and no stored folders or files.

The 128GB drive contained the OS (Win10) on C:\, a SYSTEM drive Z:\, and
an unspecified RECOVERY drive; i.e. 3 separate partitions.

Transferring the OS C:\ drive onto the 2TB drive sounds like a good
idea. I'll have to look into that. What are the major pitfalls? There
have got to be some!!! The big question is how the hell do you create a
new C:\ drive when one already exists???

One way that's frequently recommended around here, which I agree with,
is to use Macrium Reflect Free to clone C: to D:. Do the cloning
operation, then shut down. Disconnect the SSD and boot from the 2TB
drive. Shut down, reconnect the SSD, boot from the 2TB drive, format the
SSD and use it for whatever you like. Disk performance will take a hit
by going from SSD to spinning drive, but before too long you'll stop
noticing it.

God. I loved Windows XP!

The OS doesn't matter in this case.


Using a spinning drive as your windows drive when you have a perfectly
good SSD to run it on is a real dumb Idea!

I totally agree, but the OP is apparently in a tight spot. For his
system drive, does he use a drive that's very fast and way too small, or
does he use a drive that's slow and probably way bigger than it needs to
be? Neither are good choices, IMHO.

Furthermore 128 GB is plenty big enough for windows IF you don't put any
other crap on it.
I have 3 machines running Windows 10 on 128 GB SSDs and in all cases
Windows uses 27 to 32GB, lean and mean. JUST INSTALL ALL your other
stuff and data on the large spinning drive.

Again, I agree, but your use of the word "IF" is a deal breaker for me,
and possibly for the OP. I know I'm not willing to jump through those
hoops, so IMHO the minimum size for a Windows system drive is 512GB. My
use case might not apply to anyone else, however.


If changing a few drive letters is too much of a hardship for you thats
OK by me.

If you think that's all it takes that's OK by me. ;-)

On 5/8/2017 9:36 AM, Char Jackson wrote:
On Sun, 7 May 2017 10:45:06 -0500, Rene Lamontagne
wrote:

On 5/7/2017 10:20 AM, Char Jackson wrote:
On Fri, 5 May 2017 08:18:22 -0500, Rene Lamontagne
wrote:

On 5/4/2017 10:29 PM, Char Jackson wrote:
On Thu, 4 May 2017 23:27:53 +0100, jbm wrote:

On 04/05/2017 14:18, Paul wrote:
Wolf K wrote:
On 2017-05-03 18:17, jbm wrote:
[...]
Secondly, I am a bit ****ed off with HP for installing such a small
drive as their main C:\ drive.
[...]

Well, they were trying to meet a price point....


These are the specs on the HP Pavilion 550-103na Desktop PC.

Hard drive: 2 TB HDD & 128 GB SSD

I don't think that's a particular egregious setup.

If having C: on an SSD is cramping your style,
you can always move the contents of the 128GB SSD
into the 2TB HDD, resize the C: partition, done.

The 128GB SSD is likely to have the recovery partition
and the like, while the 2TB hard drive should have
hardly any valuable OEM info at all on it.

So you should be able to whip up a 1800GB C:
partition, if you want one. I think I could
do that in one shot, with Macrium Reflect Free.

http://www.macrium.com/reflectfree.asp

By placing C: on the hard drive, it won't run as
fast, but it will "suit your lifestyle" better
(if you want to "store it all" on C: ). It can be
fixed.

Paul


On delivery, the 2TB D:\ drive was empty apart from its label
DATADRIVE1. Just one partition and no stored folders or files.

The 128GB drive contained the OS (Win10) on C:\, a SYSTEM drive Z:\, and
an unspecified RECOVERY drive; i.e. 3 separate partitions.

Transferring the OS C:\ drive onto the 2TB drive sounds like a good
idea. I'll have to look into that. What are the major pitfalls? There
have got to be some!!! The big question is how the hell do you create a
new C:\ drive when one already exists???

One way that's frequently recommended around here, which I agree with,
is to use Macrium Reflect Free to clone C: to D:. Do the cloning
operation, then shut down. Disconnect the SSD and boot from the 2TB
drive. Shut down, reconnect the SSD, boot from the 2TB drive, format the
SSD and use it for whatever you like. Disk performance will take a hit
by going from SSD to spinning drive, but before too long you'll stop
noticing it.

God. I loved Windows XP!

The OS doesn't matter in this case.


Using a spinning drive as your windows drive when you have a perfectly
good SSD to run it on is a real dumb Idea!

I totally agree, but the OP is apparently in a tight spot. For his
system drive, does he use a drive that's very fast and way too small, or
does he use a drive that's slow and probably way bigger than it needs to
be? Neither are good choices, IMHO.

Furthermore 128 GB is plenty big enough for windows IF you don't put any
other crap on it.
I have 3 machines running Windows 10 on 128 GB SSDs and in all cases
Windows uses 27 to 32GB, lean and mean. JUST INSTALL ALL your other
stuff and data on the large spinning drive.

Again, I agree, but your use of the word "IF" is a deal breaker for me,
and possibly for the OP. I know I'm not willing to jump through those
hoops, so IMHO the minimum size for a Windows system drive is 512GB. My
use case might not apply to anyone else, however.


If changing a few drive letters is too much of a hardship for you thats
OK by me.

If you think that's all it takes that's OK by me. ;-)



Touche.

Rene