I'm using Windows 10 Pro, version 1703, build 15063.674.
The past week I've had a big update offered, but didn't have time to install it yet.
Search found 5 matches
- 01 Dec 2017, 14:20
- Forum: Problems and Troubleshooting
- Topic: Background process after closing
- Replies: 3
- Views: 5195
- 19 Nov 2017, 22:45
- Forum: Problems and Troubleshooting
- Topic: Background process after closing
- Replies: 3
- Views: 5195
Background process after closing
I'm on Windows 10, running version 3.0.8 (x64). Usually not in administrator mode. Whenever I close an instance of Salamander, it often keeps running as a Background Process. Regularly when it starts a "Bug Reporter" process is also started. That then also keeps running in the background. ...
- 13 Nov 2012, 20:05
- Forum: Problems and Troubleshooting
- Topic: Credentials not stored when running AS as administrator
- Replies: 2
- Views: 3591
Re: Credentials not stored when running AS as administrator
Thank you for your response. Supporting UAC would be a good thing I guess. But shouldn't Salamander store any credentials as the administrator also? I guess you're just using the credentials manager of Windows and that probably doesn't let you store credentials for the administrator. But technically...
- 03 Nov 2012, 12:16
- Forum: Problems and Troubleshooting
- Topic: Credentials not stored when running AS as administrator
- Replies: 2
- Views: 3591
Credentials not stored when running AS as administrator
I'm running Altap Salamander as Administrator (using the scheduled task trick to automatically start it with those privileges) for the few times I want to edit a file on C: (most of the time the hosts file). I have a remote share (samba) mounted on a drive and the credentials for that are stored in ...
- 09 Sep 2012, 10:21
- Forum: Feature Requests
- Topic: Work around Windows' broken file copy
- Replies: 1
- Views: 3352
Work around Windows' broken file copy
Using Salamander I was copying >1GB files from a normal HDD to a USB2.0 memory stick. Copy progress would progress very quick and then halt. Clearly the read was buffered (several 100 megabytes) and then slowly written to the USB stick. Almost all my 4GB RAM is in use (normal or cached), so there's ...