WinXP Pro - various problems

Slickone

Diamond Member
Dec 31, 1999
6,120
0
0
I have several problems w/ my XP Pro (non SP1) NTFS system. Has anyone else experienced any of these?

1. Under Display Properties->Screen Saver->Power->Power Schemes, after saving my own schemes, when I go back later (only after reboot?), they're gone.

2. Sometimes I can't restore Windows Explorer's windows that are minimized. If I left click on them in the taskbar, it does nothing (stays minized). I can right click on them in the taskbar and choose maximize, but still cant make them smaller than the maximized window. I can only maximize, minimize, or close them. It's always occured only with Windows Explorer instances.

3. None of the wallpaper JPGs that came w/ WinXP show up in my Display Properties/Desktop tab/Background box, even though they are all still located in the C:\windows\web\wallpaper folder. Only BMPs show up in the Background box.
When selecting a background from there, I've tried using the Browse button to manually point to one of the .JPGs from c:\windows\web\wallpaper, and it wouldn't load. I didn't have this problem when I first installed XP.
I have ACDSee associated w/ all picture files (incl BMP and JPG). I had StyleXP installed at one time, but have uninstalled it (problem still occured then and now though), leaving it's DLL to allow me to still add Styles.

4. I have a few files that are 0KB (from either WinMX or Grokster, xfers that never actually started), and one that is corrupt (and showing 0KB). When I try to delete these (even in safe mode), it locks Explorer. I was able to boot into Dos and delete most, but why does this happen? And with such super long strange filenames the temp downloading files in WinMX & Grokster has, it's a pain to deal w/ in DOS.


Will SP1 possibly fix any of these?
 

igiveup

Golden Member
Feb 17, 2001
1,066
0
0
1. Under Display Properties->Screen Saver->Power->Power Schemes, after saving my own schemes, when I go back later (only after reboot?), they're gone.
#1. Do you have admin rights? Have you messed with Group Policy at all? Those are the only two things that I can think of for this one.


4. I have a few files that are 0KB (from either WinMX or Grokster, xfers that never actually started), and one that is corrupt (and showing 0KB). When I try to delete these (even in safe mode), it locks Explorer. I was able to boot into Dos and delete most, but why does this happen? And with such super long strange filenames the temp downloading files in WinMX & Grokster has, it's a pain to deal w/ in DOS.
#4. del begginningoffilename*.mp3

That should keep you from typing the whole damn thing. Works in Linux too. How I install most RPM's since the names are usually 30 characters or more. Just make sure the first part of the filename is unique or the wrong file will be deleted.

You know, this stuff is really so off the wall that if it was me I would re-install. I don't THINK that this stuff is fixed in SP1, but I don't know for sure. Review this page on Microsoft's site to see if any of this is fixed. Like I said though, your problems aren't ones that I have run into prior to a service pack being applied.
 

ProviaFan

Lifer
Mar 17, 2001
14,993
1
0
Originally posted by: igiveup
#4. del begginningoffilename*.mp3

That should keep you from typing the whole damn thing. Works in Linux too.
That works in Windows, but in Linux I believe you need to "rm beginning*.mp3" instead, unless your shell translates "del" into "rm", or there is a symlink. Distros may use symlinks for that, but be safe and do it the real UNIX way - with "rm" :)
 

SoulAssassin

Diamond Member
Feb 1, 2001
6,135
2
0
Originally posted by: jliechty
Originally posted by: igiveup
#4. del begginningoffilename*.mp3

That should keep you from typing the whole damn thing. Works in Linux too.
That works in Windows, but in Linux I believe you need to "rm beginning*.mp3" instead, unless your shell translates "del" into "rm", or there is a symlink. Distros may use symlinks for that, but be safe and do it the real UNIX way - with "rm" :)

I think he was referring to the use of wildcards, not the actual command.