Jim Dell <Jim.Dell@gmail.com> wrote:
[...]

Thanks for all the suggestions
I have written a batch file that deletes all the folders & Files under
%TEMP%
I don't have Opera browser installed, so it's not the cause of the
scoped folders

You're of course free to use your batch file, but see VanguardLH's
response [1] and my response to it [2], which explains that Windows
already cleans the %TEMP% folder if you tick [3] a tickmark in Settings.

[1] Message-ID: <sfiuwyjydahk$.dlg@v.nguard.lh>

[2] Message-ID: <vppss0.ddo.1@ID-201911.user.individual.net>

[3] On my (Windows 11) system the tickmark was ticked by default.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2/26/2025 9:12 AM, Jim Dell wrote:

Got a question about the files in %TEMP%

There are thousands of them on my system

If you run “dir %TEMP%” from a command prompt you’ll see them.

Mostly mine are
HeadlessChrome304648710500
scoped_dir304_1457881672
folders

The only thing that changes is the numbers after the text.

Yes, a run a Chrome Headless job. Is there a parameter to set to I
should set to prevent the HeadlessChrome folders?

I don’t know what is causing the scoped_dir folders from being created.

Any help would be appreciated.

Jim

Just to add info note that the MS Defender log is kept in C:\Users\xxx\AppData\Local\Temp\MpCmdRun.log

It is one log where Defender actions are appended and if you do not move
it out of Temp it will restart after every deletion and not be available
for past actions reference.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

John C. <r9jmg0@yahoo.com> wrote:

Here's what I do on a regular basis:

1. Open the c:\windows\temp folder in File Explorer
2. Click on any file in the right hand pane to select it
3. Press Control-A to select everything in the c:\windows\temp folder
4. Press the Delete key

Some files may refuse to be deleted if your system has crashed at any
point, but the vast majority of the files will go to your Recycle Bin.

5. Right click on your Recycle Bin
6. Select "Empty Recycle Bin"

Note that the OP's (Jim Dell) issue is about the %TEMP% folder, not
about C:\Windows\Temp.

That said, the automatic cleaning of %TEMP% which VanguardLH mentioned
[1], *also* cleans C:\Windows\Temp, so while anybody is of course
free to do it themselves/manually, I think there is no real reason.

I hate to bring it to you, but Windows is not *all* bad! :-)

[1] See my pointers to VanguardLH's and my responses in
Message-ID: <vpq25k.2go.1@ID-201911.user.individual.net>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

TmV3eWFuYTIgd3JvdGU6DQo+IE9uIDIvMjcvMjAyNSA2OjE1IEFNLCBFZCBDcnllciB3cm90 ZToNCj4gDQo+PiBJIHJlZ3VsYXJseSBlbXB0eSBteSBUZW1wIGZpbGUgaW4gdXNlcnMvIEFw cGRhdGEvIExvY2FsLiBJIGp1c3QgZ28gDQo+PiB0aGVyZSwgc2VsZWN0IGFsbCwgYW5kIGRl bGV0ZS4gT25lIGZpbGUgd29uJ3QgZGVsZXRlOyBGWFNBUHwgDQo+PiBEZWJ1Z0xvZ0ZpbGUs IGFzc29jaWF0ZWQgd2l0aCBXaW5kb3dzIEZheC4NCj4+IEkgZG9uJ3QgdXNlIENocm9tZSwg YnV0IEVkZ2UgcHV0cyBsb3RzIG9mIHJ1YmJpc2ggaW4gdGhlcmUsIGFuZCBldmVuIA0KPj4g YWZ0ZXIgYSBjb3VwbGUgb2YgZGF5cyBmcm9tIGVtcHR5IGl0IHdpbGwgYnVpbGQgdG8gMTAw TUIuIFdoeSBjYW4ndCANCj4+IGNvbXB1dGVyIHByb2dyYW1tZXJzIGNsZWFuIHVwIHRoZWly IG1lc3M/IFRoZXkncmUgYXMgYmFkIGFzIGJ1aWxkZXJzLiANCj4+IEkgb25jZSBjb21wbGFp bmVkIHRvIGEgYnVpbGRlciBhYm91dCB0aGF0LCBhbmQgaGUgc2FpZCAiT2gsIHlvdSBtZWFu IA0KPj4gdGhlIGJpdHM/Ig0KPj4gKDotwqAgQml0cyB0byBoaW07IGEgY2xlYW4tdXAgam9i IGZvciBtZSENCj4+DQo+IA0KPiAgwqBIZSBwcm9iYWJseSBoYXMgYSB3aWZlIHdobyBwaWNr cyB1cCBhZnRlciBoaW0uDQo+PiBZb3UgbWVudGlvbiBhIHNjcmlwdC4gT3RoZXJzIGhhdmUg bWVudGlvbmVkIG90aGVyIHNjcmlwdHMuIEknZCBiZSANCj4+IGludGVyZXN0ZWQgaW4gdGhl IGJlc3QgYXZhaWxhYmxlLg0KPj4gVG8gYWxsOyBJZiB5b3UgdGhpbmsgeW91IGhhdmUgdGhl IGJlc3QsIHBvc3QgaGVyZSBhbmQgSSdsbCB0cnkgdGhlbS4NCj4+DQo+IA0KPiAgwqBJIHdy b3RlIGEgc2NyaXB0IG9uIFhQIGJlY2F1c2UgZGVsZXRpbmcgYnkgaGFuZCB3b3VsZCBvZnRl bg0KPiBnZXQgc3RvcHBlZCB3aGVuIG9uZSBmaWxlIHdvdWxkbid0IGRlbGV0ZS4gU28gaXQg d2FzIGVhc2llciB0bw0KPiB3cml0ZSBhIFZCU2NyaXB0IHRoYXQgd291bGQga2VlcCBnb2lu ZyB3aGVuIGl0IGhpdCBhIGZpbGUgaXQNCj4gY291bGRuJ3QgZGVsZXRlLiBUaGVyZSB3ZXJl IGFsc28gMyBURU1QIGZvbGRlcnMuIEM6XCwNCj4gQzpcV2luZG93cyBhbmQgdGhlIGFwcGRh dGEgVEVNUC4gT24gV2luMTAgdGhlcmUncyBzdGlsbA0KPiBDOlxXaW5kb3dzXFRFTVAuIE15 IEludGVsIGdyYXBoaWNzIGlzIHVzaW5nIGl0IG5vdy4NCj4gDQo+ICDCoCBNeSBzY3JpcHQg aXMgbm90aGluZyBzcGVjaWFsLiBJdCBqdXN0IGdvZXMgdGhyb3VnaCBkZWxldGluZw0KPiB3 aGF0IGl0IGNhbiwgZ2l2ZXMgbWUgYSByZXBvcnQsIHRoZW4gc2hvd3MgYSBtZXNzYWdlIHRv IHJ1bg0KPiBEaXNtLmV4ZSAvb25saW5lIC9DbGVhbnVwLUltYWdlIC9TdGFydENvbXBvbmVu dENsZWFudXAgL1Jlc2V0QmFzZQ0KPiBpbiBvcmRlciB0byBjbGVhbiBhbnl0aGluZyB1bm5l Y2Vzc2FyeSBvdXQgb2Ygd2luc3hzLg0KPiANCj4gDQoNClRoYXQgb25lIGZvbGRlciBpcyBh bHdheXMgdGhlIG9ubHkgb25lIHRoYXQgaXMgc3lzdGVtLWxvY2tlZCBhbmQgDQp1bmRlbGV0 YWJsZS4gQnV0IGl0IHByb3ZpZGVzIGxpdHRsZSBob2xkLXVwLCBzaW5jZSBXaW5FeHBsb3Jl ciB0ZWxscyBtZSANCml0IGNhbid0IGRlbGV0ZSBpdCwgZ2l2ZXMgbWUgaGlnaGxpZ2h0LCBh bmQgd2hlbiBJIGhpdCBvayBpdCdzIHRoZSBvbmx5IA0Kb25lIGxlZnQ7IGpvYiBmaW5pc2hl ZC4NCg0KSSBuZXZlciBnZXQgbXVjaCBkZWJyaXMgaW4gdGhlIG90aGVyIHR3byBmb2xkZXJz LiBUaGUgQzpcV2luZG93cyBUZW1wIA0KZ2V0cyBzb21lLCBidXQgc29tZXRoaW5nIG90aGVy IHRoYW4gbWUgZGVsZXRlcyBpdCBvY2Nhc2lvbmFsbHkuDQoNCkVkDQo=

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jim Dell wrote:

Got a question about the files in %TEMP%

There are thousands of them on my system

If you run “dir %TEMP%” from a command prompt you’ll see them.

Mostly mine are
HeadlessChrome304648710500
scoped_dir304_1457881672
folders

The only thing that changes is the numbers after the text.

Yes, a run a Chrome Headless job. Is there a parameter to set to I
should set to prevent the HeadlessChrome folders?

I don’t know what is causing the scoped_dir folders from being created.

Any help would be appreciated.

Jim

Here's what I do on a regular basis:

1. Open the c:\windows\temp folder in File Explorer
2. Click on any file in the right hand pane to select it
3. Press Control-A to select everything in the c:\windows\temp folder
4. Press the Delete key

Some files may refuse to be deleted if your system has crashed at any
point, but the vast majority of the files will go to your Recycle Bin.

5. Right click on your Recycle Bin
6. Select "Empty Recycle Bin"

I would try to find out what's causing the Temp folder to get flooded
with those "HeadlessChrome" folders. Sound like something that Google
Chrome is creating, if you have Google Chrome installed.

I've never used Google Chrome -hated it from when I first heard about
it- so I couldn't tell you if that's the source.

--
John C.

Take back Microsoft from India.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2/27/2025 2:00 PM, Ed Cryer wrote:

Newyana2 wrote:

On 2/27/2025 6:15 AM, Ed Cryer wrote:

I regularly empty my Temp file in users/ Appdata/ Local. I just go
there, select all, and delete. One file won't delete; FXSAP|
DebugLogFile, associated with Windows Fax.
I don't use Chrome, but Edge puts lots of rubbish in there, and even
after a couple of days from empty it will build to 100MB. Why can't
computer programmers clean up their mess? They're as bad as builders.
I once complained to a builder about that, and he said "Oh, you mean
the bits?"
(:-� Bits to him; a clean-up job for me!

��He probably has a wife who picks up after him.

You mention a script. Others have mentioned other scripts. I'd be
interested in the best available.
To all; If you think you have the best, post here and I'll try them.

��I wrote a script on XP because deleting by hand would often
get stopped when one file wouldn't delete. So it was easier to
write a VBScript that would keep going when it hit a file it
couldn't delete. There were also 3 TEMP folders. C:\,
C:\Windows and the appdata TEMP. On Win10 there's still
C:\Windows\TEMP. My Intel graphics is using it now.

�� My script is nothing special. It just goes through deleting
what it can, gives me a report, then shows a message to run
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
in order to clean anything unnecessary out of winsxs.

That one folder is always the only one that is system-locked and
undeletable. But it provides little hold-up, since WinExplorer tells me
it can't delete it, gives me highlight, and when I hit ok it's the only
one left; job finished.

I never get much debris in the other two folders. The C:\Windows Temp
gets some, but something other than me deletes it occasionally.

I just had an interesting experience. My system somehow grew to
22.6 GB -- about 2 GB too big. I looked around and found that the
TEMP folder in winsxs is not emptied by any means. I thought
my DISM line cleaned it, but it turns out what that does is to delete
unneeded old versions of updates and components. In some cases
it can clean up a great deal, especially if you allow Windows Update.

But nothing cleans TEMP. I looked online. How to delete winsxs\temp\InFlight, which had grown to nearly 4 GB, and all the
files seemed to be dated 2/10. What did I do on 2/10? Beats me.
Is it safe to delete those files? I couldn't find any definitive answer.

Finally I made a current disk image, rebooted, used my handy
utility to remove restrictions from all 12K files(!), and deleted InFlight.
No problems that I can see. Apparently there are some things that
get stuck there. What really strikes me is that so much documentation
is missing for Win10. It's 10 years old. I used to know prety much
everything on 98 and XP. On 10 I find endless folders with mysterious
names, containing files that are equally mysterious. And no one seems
to know what they are. So much crap.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

TmV3eWFuYTIgd3JvdGU6DQo+IE9uIDIvMjcvMjAyNSAyOjAwIFBNLCBFZCBDcnllciB3cm90 ZToNCj4+IE5ld3lhbmEyIHdyb3RlOg0KPj4+IE9uIDIvMjcvMjAyNSA2OjE1IEFNLCBFZCBD cnllciB3cm90ZToNCj4+Pg0KPj4+PiBJIHJlZ3VsYXJseSBlbXB0eSBteSBUZW1wIGZpbGUg aW4gdXNlcnMvIEFwcGRhdGEvIExvY2FsLiBJIGp1c3QgZ28gDQo+Pj4+IHRoZXJlLCBzZWxl Y3QgYWxsLCBhbmQgZGVsZXRlLiBPbmUgZmlsZSB3b24ndCBkZWxldGU7IEZYU0FQfCANCj4+ Pj4gRGVidWdMb2dGaWxlLCBhc3NvY2lhdGVkIHdpdGggV2luZG93cyBGYXguDQo+Pj4+IEkg ZG9uJ3QgdXNlIENocm9tZSwgYnV0IEVkZ2UgcHV0cyBsb3RzIG9mIHJ1YmJpc2ggaW4gdGhl cmUsIGFuZCBldmVuIA0KPj4+PiBhZnRlciBhIGNvdXBsZSBvZiBkYXlzIGZyb20gZW1wdHkg aXQgd2lsbCBidWlsZCB0byAxMDBNQi4gV2h5IGNhbid0IA0KPj4+PiBjb21wdXRlciBwcm9n cmFtbWVycyBjbGVhbiB1cCB0aGVpciBtZXNzPyBUaGV5J3JlIGFzIGJhZCBhcyANCj4+Pj4g YnVpbGRlcnMuIEkgb25jZSBjb21wbGFpbmVkIHRvIGEgYnVpbGRlciBhYm91dCB0aGF0LCBh bmQgaGUgc2FpZCANCj4+Pj4gIk9oLCB5b3UgbWVhbiB0aGUgYml0cz8iDQo+Pj4+ICg6LcKg IEJpdHMgdG8gaGltOyBhIGNsZWFuLXVwIGpvYiBmb3IgbWUhDQo+Pj4+DQo+Pj4NCj4+PiDC oMKgSGUgcHJvYmFibHkgaGFzIGEgd2lmZSB3aG8gcGlja3MgdXAgYWZ0ZXIgaGltLg0KPj4+ PiBZb3UgbWVudGlvbiBhIHNjcmlwdC4gT3RoZXJzIGhhdmUgbWVudGlvbmVkIG90aGVyIHNj cmlwdHMuIEknZCBiZSANCj4+Pj4gaW50ZXJlc3RlZCBpbiB0aGUgYmVzdCBhdmFpbGFibGUu DQo+Pj4+IFRvIGFsbDsgSWYgeW91IHRoaW5rIHlvdSBoYXZlIHRoZSBiZXN0LCBwb3N0IGhl cmUgYW5kIEknbGwgdHJ5IHRoZW0uDQo+Pj4+DQo+Pj4NCj4+PiDCoMKgSSB3cm90ZSBhIHNj cmlwdCBvbiBYUCBiZWNhdXNlIGRlbGV0aW5nIGJ5IGhhbmQgd291bGQgb2Z0ZW4NCj4+PiBn ZXQgc3RvcHBlZCB3aGVuIG9uZSBmaWxlIHdvdWxkbid0IGRlbGV0ZS4gU28gaXQgd2FzIGVh c2llciB0bw0KPj4+IHdyaXRlIGEgVkJTY3JpcHQgdGhhdCB3b3VsZCBrZWVwIGdvaW5nIHdo ZW4gaXQgaGl0IGEgZmlsZSBpdA0KPj4+IGNvdWxkbid0IGRlbGV0ZS4gVGhlcmUgd2VyZSBh bHNvIDMgVEVNUCBmb2xkZXJzLiBDOlwsDQo+Pj4gQzpcV2luZG93cyBhbmQgdGhlIGFwcGRh dGEgVEVNUC4gT24gV2luMTAgdGhlcmUncyBzdGlsbA0KPj4+IEM6XFdpbmRvd3NcVEVNUC4g TXkgSW50ZWwgZ3JhcGhpY3MgaXMgdXNpbmcgaXQgbm93Lg0KPj4+DQo+Pj4gwqDCoCBNeSBz Y3JpcHQgaXMgbm90aGluZyBzcGVjaWFsLiBJdCBqdXN0IGdvZXMgdGhyb3VnaCBkZWxldGlu Zw0KPj4+IHdoYXQgaXQgY2FuLCBnaXZlcyBtZSBhIHJlcG9ydCwgdGhlbiBzaG93cyBhIG1l c3NhZ2UgdG8gcnVuDQo+Pj4gRGlzbS5leGUgL29ubGluZSAvQ2xlYW51cC1JbWFnZSAvU3Rh cnRDb21wb25lbnRDbGVhbnVwIC9SZXNldEJhc2UNCj4+PiBpbiBvcmRlciB0byBjbGVhbiBh bnl0aGluZyB1bm5lY2Vzc2FyeSBvdXQgb2Ygd2luc3hzLg0KPj4+DQo+Pj4NCj4+DQo+PiBU aGF0IG9uZSBmb2xkZXIgaXMgYWx3YXlzIHRoZSBvbmx5IG9uZSB0aGF0IGlzIHN5c3RlbS1s b2NrZWQgYW5kIA0KPj4gdW5kZWxldGFibGUuIEJ1dCBpdCBwcm92aWRlcyBsaXR0bGUgaG9s ZC11cCwgc2luY2UgV2luRXhwbG9yZXIgdGVsbHMgDQo+PiBtZSBpdCBjYW4ndCBkZWxldGUg aXQsIGdpdmVzIG1lIGhpZ2hsaWdodCwgYW5kIHdoZW4gSSBoaXQgb2sgaXQncyB0aGUgDQo+ PiBvbmx5IG9uZSBsZWZ0OyBqb2IgZmluaXNoZWQuDQo+Pg0KPj4gSSBuZXZlciBnZXQgbXVj aCBkZWJyaXMgaW4gdGhlIG90aGVyIHR3byBmb2xkZXJzLiBUaGUgQzpcV2luZG93cyBUZW1w IA0KPj4gZ2V0cyBzb21lLCBidXQgc29tZXRoaW5nIG90aGVyIHRoYW4gbWUgZGVsZXRlcyBp dCBvY2Nhc2lvbmFsbHkuDQo+Pg0KPiANCj4gIMKgwqAgSSBqdXN0IGhhZCBhbiBpbnRlcmVz dGluZyBleHBlcmllbmNlLiBNeSBzeXN0ZW0gc29tZWhvdyBncmV3IHRvDQo+IDIyLjYgR0Ig LS0gYWJvdXQgMiBHQiB0b28gYmlnLiBJIGxvb2tlZCBhcm91bmQgYW5kIGZvdW5kIHRoYXQg dGhlDQo+IFRFTVAgZm9sZGVyIGluIHdpbnN4cyBpcyBub3QgZW1wdGllZCBieSBhbnkgbWVh bnMuIEkgdGhvdWdodA0KPiBteSBESVNNIGxpbmUgY2xlYW5lZCBpdCwgYnV0IGl0IHR1cm5z IG91dCB3aGF0IHRoYXQgZG9lcyBpcyB0byBkZWxldGUNCj4gdW5uZWVkZWQgb2xkIHZlcnNp b25zIG9mIHVwZGF0ZXMgYW5kIGNvbXBvbmVudHMuIEluIHNvbWUgY2FzZXMNCj4gaXQgY2Fu IGNsZWFuIHVwIGEgZ3JlYXQgZGVhbCwgZXNwZWNpYWxseSBpZiB5b3UgYWxsb3cgV2luZG93 cyBVcGRhdGUuDQo+IA0KPiAgwqAgQnV0IG5vdGhpbmcgY2xlYW5zIFRFTVAuIEkgbG9va2Vk IG9ubGluZS4gSG93IHRvIGRlbGV0ZQ0KPiB3aW5zeHNcdGVtcFxJbkZsaWdodCwgd2hpY2gg aGFkIGdyb3duIHRvIG5lYXJseSA0IEdCLCBhbmQgYWxsIHRoZQ0KPiBmaWxlcyBzZWVtZWQg dG8gYmUgZGF0ZWQgMi8xMC4gV2hhdCBkaWQgSSBkbyBvbiAyLzEwPyBCZWF0cyBtZS4NCj4g SXMgaXQgc2FmZSB0byBkZWxldGUgdGhvc2UgZmlsZXM/IEkgY291bGRuJ3QgZmluZCBhbnkg ZGVmaW5pdGl2ZSBhbnN3ZXIuDQo+IA0KPiAgwqAgRmluYWxseSBJIG1hZGUgYSBjdXJyZW50 IGRpc2sgaW1hZ2UsIHJlYm9vdGVkLCB1c2VkIG15IGhhbmR5DQo+IHV0aWxpdHkgdG8gcmVt b3ZlIHJlc3RyaWN0aW9ucyBmcm9tIGFsbCAxMksgZmlsZXMoISksIGFuZCBkZWxldGVkIElu RmxpZ2h0Lg0KPiBObyBwcm9ibGVtcyB0aGF0IEkgY2FuIHNlZS4gQXBwYXJlbnRseSB0aGVy ZSBhcmUgc29tZSB0aGluZ3MgdGhhdA0KPiBnZXQgc3R1Y2sgdGhlcmUuIFdoYXQgcmVhbGx5 IHN0cmlrZXMgbWUgaXMgdGhhdCBzbyBtdWNoIGRvY3VtZW50YXRpb24NCj4gaXMgbWlzc2lu ZyBmb3IgV2luMTAuIEl0J3MgMTAgeWVhcnMgb2xkLiBJIHVzZWQgdG8ga25vdyBwcmV0eSBt dWNoDQo+IGV2ZXJ5dGhpbmcgb24gOTggYW5kIFhQLiBPbiAxMCBJIGZpbmQgZW5kbGVzcyBm b2xkZXJzIHdpdGggbXlzdGVyaW91cw0KPiBuYW1lcywgY29udGFpbmluZyBmaWxlcyB0aGF0 IGFyZSBlcXVhbGx5IG15c3RlcmlvdXMuIEFuZCBubyBvbmUgc2VlbXMNCj4gdG8ga25vdyB3 aGF0IHRoZXkgYXJlLiBTbyBtdWNoIGNyYXAuDQo+IA0KDQpNeSBXaW4xMCBib3ggb2YgdHJp Y2tzIGlzIG92ZXIgMTAgeWVhcnMgb2xkLCBidXQgSSBzdGljayB3aXRoIGl0LiBJdCBoYXMg DQphIDUwMEdCIFNTRCwgOEdCIFJBTSwgQ1BVIGFzIG9sZCBhcyBOb2FoLCBhbmQgaXQgc3Rp bGwgZnVuY3Rpb25zIHF1aWNrbHkgDQplbm91Z2ggYW5kIHdlbGwgZW5vdWdoIGZvciBteSBt b2RlcmF0ZSBjb21wdXRpbmcgbmVlZHMuDQpUaGUgU1NEIGlzIGxpdHRlcmVkIHdpdGggZmls ZXMgb2YgZXZlcnkgZGVzY3JpcHRpb247IG1hbnkgZW1wdHkgZm9sZGVycywgDQpsb3RzIG9m IHVuaW5zdGFsbCBsZWZ0LW92ZXJzLCBhbmQgR29kIGtub3dzIHdoYXQgZWxzZS4gSnVzdCBz aW1wbHkgDQpsaXN0aW5nIHRocm91Z2ggdGhlIGZpbGUgdHlwZXMgaW5zdGFsbGVkIGlzIHN1 ZmZpY2llbnQgcHJvb2Ygb2YgYWxsIHRoZSANCmxpdHRlci4gTW9zdCBvZiB0aGUgb25lcyBs aXN0ZWQgcmluZyBubyBiZWxsIGF0IGFsbC4NCg0KSSBkb24ndCBrbm93IHdoeSBJIGV2ZW4g Ym90aGVyIGVtcHR5aW5nIEFwcGRhdGFcIFRlbXAgb2NjYXNpb25hbGx5LiBUaGF0IA0KaG9s ZHMganVzdCBhIGZyYWN0aW9uIG9mIGFsbCB0aGUgZ3VtcGggYW5kIGdhZ2dhIHRvIGJlIGZv dW5kLg0KVGhlIHRoaW5nIGlzLCB0aG91Z2gsIHRoYXQgdGhlIFNTRCBpcyBsZXNzIHRoYW4g aGFsZiBmdWxsLg0KSXQncyBtZXJlIGhhYml0IHdpdGggdGhlIFRFTVAgZm9sZGVyLg0KSSBo b3BlIEkgZG9uJ3QgZ2V0IHNvbWUgaXRjaCB0byB0aWR5IHVwIHByb3Blcmx5LiBJJ2QgcHJv YmFibHkgYmUgYWJsZSANCnRvIGNsZWFyIG91dCBzZXZlcmFsIGh1bmRyZWQgR0JzLiBCdXQs IHdoaWxlIGRvaW5nIHRoYXQsIEkgbWlnaHQgZGlzdHVyYiANCnNvbWV0aGluZyB0aGF0IG1p Z2h0IGNvc3QgbWUgaG91cnMgb2YgdGltZSB0byByZXN0b3JlLg0KU28gdGhlbiwgcXVvZCBu b24gZnJhY3R1bSBlc3QsIG5vbGkgdGFuZ2VyZS4NCg0KRWQNCg0KRWQNCg==

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Frank Slootweg wrote:

John C. wrote:

Here's what I do on a regular basis:

1. Open the c:\windows\temp folder in File Explorer
2. Click on any file in the right hand pane to select it
3. Press Control-A to select everything in the c:\windows\temp folder
4. Press the Delete key

Some files may refuse to be deleted if your system has crashed at any
point, but the vast majority of the files will go to your Recycle Bin.

5. Right click on your Recycle Bin
6. Select "Empty Recycle Bin"

Note that the OP's (Jim Dell) issue is about the %TEMP% folder, not
about C:\Windows\Temp.

Thanks. And I guess that means he meant a C:\WINDOWS\system32\%TEMP%
folder or C:\WINDOWS\system32\TEMP folder.

I have only a c:\windows\temp folder in the Windows folder.

That said, the automatic cleaning of %TEMP% which VanguardLH mentioned
[1], *also* cleans C:\Windows\Temp, so while anybody is of course
free to do it themselves/manually, I think there is no real reason.

I hate to bring it to you, but Windows is not *all* bad! :-)

[1] See my pointers to VanguardLH's and my responses in
Message-ID: <vpq25k.2go.1@ID-201911.user.individual.net>

When I run “dir %TEMP%” in Powershell, I get: _________________________________________________________________________________
dir : Cannot find path 'C:\WINDOWS\system32\%TEMP%' because it does not
exist.
At line:1 char:1
+ dir %TEMP%
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\WINDOWS\system32\%TEMP%:String) [Get-ChildItem], ItemNotFoundExcepti
on
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand _________________________________________________________________________________

If Jim was talking about the temp folder here:

Users\[Your Username]\AppData\Local\Temp

I regularly clean it the same way that I do the temp folder in the
Windows folder.

--
John C.

Take back Microsoft from India.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 2/28/2025 8:29 AM, John C. wrote:

Frank Slootweg wrote:

John C. wrote:

Here's what I do on a regular basis:

1. Open the c:\windows\temp folder in File Explorer
2. Click on any file in the right hand pane to select it
3. Press Control-A to select everything in the c:\windows\temp folder
4. Press the Delete key

Some files may refuse to be deleted if your system has crashed at any
point, but the vast majority of the files will go to your Recycle Bin.

5. Right click on your Recycle Bin
6. Select "Empty Recycle Bin"

Note that the OP's (Jim Dell) issue is about the %TEMP% folder, not
about C:\Windows\Temp.

Thanks. And I guess that means he meant a C:\WINDOWS\system32\%TEMP%
folder or C:\WINDOWS\system32\TEMP folder.

I have only a c:\windows\temp folder in the Windows folder.

That said, the automatic cleaning of %TEMP% which VanguardLH mentioned
[1], *also* cleans C:\Windows\Temp, so while anybody is of course
free to do it themselves/manually, I think there is no real reason.

I hate to bring it to you, but Windows is not *all* bad! :-)

[1] See my pointers to VanguardLH's and my responses in
Message-ID: <vpq25k.2go.1@ID-201911.user.individual.net>

When I run “dir %TEMP%” in Powershell, I get: _________________________________________________________________________________
dir : Cannot find path 'C:\WINDOWS\system32\%TEMP%' because it does not exist.
At line:1 char:1
+ dir %TEMP%
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\WINDOWS\system32\%TEMP%:String) [Get-ChildItem], ItemNotFoundExcepti
on
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand _________________________________________________________________________________

If Jim was talking about the temp folder here:

Users\[Your Username]\AppData\Local\Temp

I regularly clean it the same way that I do the temp folder in the
Windows folder.

Well, you're not supposed to run anything in Powershell, now are you :-)

%temp% can be parsed by the Command Prompt shell.
That does not mean Powershell will accept it.

After a web page filled with suggestions didn't work
for Powershell, I tried this:

echo $env:temp

See if that works.

Or you could try

cd $env:temp

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

"John C." <r9jmg0@yahoo.com> wrote:

When I run �dir %TEMP%� in Powershell, I get:

dir : Cannot find path 'C:\WINDOWS\system32\%TEMP%' because it does not exist.

As a script interpreter, Powershell uses its own command set, like Get-Children, instead of the DOS commands in the DOS command interpreter (cmd.exe), like dir. Powershell does have some aliases on DOS commands,
like dir. Powershell isn't a more robust command interpreter. It is a
script processor that is tied into .NET [Framework].

https://en.wikipedia.org/wiki/PowerShell

While Powershell and cmd both use console windows to load command shells
in which to execute inputted commands and display stdout, they are very different animals: one is a domestic cat that runs from dogs while the
other is a jaguar that will take on crocodiles. I've had little use for Powershell other than occasionally to do a command that is not available
in cmd.exe, run scripts that would never be possible in batch scripts
using cmd.exe, or to exercise system functions that are obtuse or
missing from other system utilities.

As such, Powershell operates differently on DOS environment variables.
For example, instead of using the DOS command 'set varname=varvalue", in Powershell you use $Env:varname = 'varvalue'.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.5

Unless you're willing to spend the effort and time to learn a new
scripting & system interpreter language, stay away from Powershell.
Learning it is tantamount to learning a new programming language, like
Perl, Javascript, Python, VBA, PHP, ,etc. Just use a DOS shell via
cmd.exe to run the commands and use the syntax to which you are
accustomed.

Load cmd.exe to open a console window in which the command shell
operates, and then issue your DOS commands. Stick with what you know,
or spend time learning Powershell which can take a very long time
considering how vast are its features since Powershell is built on .NET
CLR (Common Language Runtime) where all inputs and outputs are .NET
objects. I'm guessing you don't want to learn .NET nor Powershell.
Learning Powershell is on my to-do list, and I even have a wishlist of
books at my local public library on learning Powershell, but I never
manage to get the time nor motivation to delve much into it.

If you don't want to read books or online tutorials on Powershell to
learn it, go through all the tribulation of testing its use, and spend
time in forums or newsgroups trying to get help, you can find classes on Powershell. IT folks who are newsbies to Powershell take 2 weeks to
learn an intro to /some/ of Powershell, mostly to facilitate their
sysadmin tasks. Most impetus to learn Powershell is by those interested
in the realm of system administration. Of course, to newbies even DOS
commands are a chore to learn, and then discover their anomalies.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Mr Xi Ji Ping <ping@china.cn> wrote:

John C. wrote:

When I run "��dir %TEMP%"�� in Powershell, I get:

You don't run anything to search for the folder. You simply type
"%TEMP%" in the search box and the folder will open for you automatically.

Have you got a Search box in the taskbar or have you removed it because Indians were spying on you? Please advise.

You can enter %temp% in any address bar managed by File Explorer, like
File Explorer's own address bar, or the address bar toolbar in the
Taskbar. In the Start Menu (with or without the search box), entering
%temp (before you even append the second %) will show a hit on the
Temporary File Folder.

The search box for the Start Menu is superfluous. Whether you type into
the search box when the Start Menu is displayed, or don't have a search
box but start typing when the Start Menu is displayed, the Start Menu
will search on whatever you type when it is in focus. The search box is
a waste of screen realestate. Just open the Start Menu, and start
typing. To hide the superfluous search box, right-click on empty space
in the Taskbar, and under the Search menu entry elect Hidden.

No idea why John used Powershell to run DOS commands. Powershell is not
the cmd.exe shell. If he insists on opening a console window for
Powershell, and to avoid learning Powershell, he could enter cmd to load
yet another shell in which to run DOS commands.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28/02/2025 13:29, John C. wrote:

When I run “dir %TEMP%” in Powershell, I get:

You don't run anything to search for the folder. You simply type
"%TEMP%" in the search box and the folder will open for you automatically.

Have you got a Search box in the taskbar or have you removed it because
Indians were spying on you? Please advise.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 27 Feb 2025 06:43:38 -0800, "John C." <r9jmg0@yahoo.com>
wrote:

Jim Dell wrote:

Got a question about the files in %TEMP%

There are thousands of them on my system

If you run “dir %TEMP%” from a command prompt you’ll see them.

Mostly mine are
HeadlessChrome304648710500
scoped_dir304_1457881672
folders

The only thing that changes is the numbers after the text.

Yes, a run a Chrome Headless job. Is there a parameter to set to I
should set to prevent the HeadlessChrome folders?

I don’t know what is causing the scoped_dir folders from being created.

Any help would be appreciated.

Jim

Here's what I do on a regular basis:

1. Open the c:\windows\temp folder in File Explorer
2. Click on any file in the right hand pane to select it
3. Press Control-A to select everything in the c:\windows\temp folder
4. Press the Delete key

Some files may refuse to be deleted if your system has crashed at any
point, but the vast majority of the files will go to your Recycle Bin.

I use PowerDesj instead of Exploder so I have a one-click "kill this
forever" button as well as a Recycle one. The kill button nukes files permanently. There is no getting them back.

5. Right click on your Recycle Bin
6. Select "Empty Recycle Bin"

I would try to find out what's causing the Temp folder to get flooded
with those "HeadlessChrome" folders. Sound like something that Google
Chrome is creating, if you have Google Chrome installed.

I've never used Google Chrome -hated it from when I first heard about
it- so I couldn't tell you if that's the source.

https://www.startpage.com/do/dsearch?q=HeadlessChrome&cat=web&language=english has loads of suggestions as to where those may be coming from.

"Headless Chrome" seems to also be a program.

J.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Newyana2 <newyana@invalid.nospam> wrote:
[...]

What really strikes me is that so much documentation
is missing for Win10. It's 10 years old. I used to know prety much
everything on 98 and XP. On 10 I find endless folders with mysterious
names, containing files that are equally mysterious. And no one seems
to know what they are. So much crap.

FWIW, when I (re)search some Windows related issue in Google, quite
often useful answers are found in https://learn.microsoft.com/en-us/...
pages. So that seems to be the kind of Windows documentation you're
missing.

I use Google to find the pages on Microsoft Learn site. I have not
tried (no need sofar) to browse/search the site itself.

Hope this helps.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Paul wrote:

John C. wrote:

Frank Slootweg wrote:

John C. wrote:

Here's what I do on a regular basis:

1. Open the c:\windows\temp folder in File Explorer
2. Click on any file in the right hand pane to select it
3. Press Control-A to select everything in the c:\windows\temp folder
4. Press the Delete key

Some files may refuse to be deleted if your system has crashed at any
point, but the vast majority of the files will go to your Recycle Bin. >>>>
5. Right click on your Recycle Bin
6. Select "Empty Recycle Bin"

Note that the OP's (Jim Dell) issue is about the %TEMP% folder, not
about C:\Windows\Temp.

Thanks. And I guess that means he meant a C:\WINDOWS\system32\%TEMP%
folder or C:\WINDOWS\system32\TEMP folder.

I have only a c:\windows\temp folder in the Windows folder.

That said, the automatic cleaning of %TEMP% which VanguardLH mentioned >>> [1], *also* cleans C:\Windows\Temp, so while anybody is of course
free to do it themselves/manually, I think there is no real reason.

I hate to bring it to you, but Windows is not *all* bad! :-)

[1] See my pointers to VanguardLH's and my responses in
Message-ID: <vpq25k.2go.1@ID-201911.user.individual.net>

When I run “dir %TEMP%” in Powershell, I get:
_________________________________________________________________________________
dir : Cannot find path 'C:\WINDOWS\system32\%TEMP%' because it does not
exist.
At line:1 char:1
+ dir %TEMP%
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound:
(C:\WINDOWS\system32\%TEMP%:String) [Get-ChildItem], ItemNotFoundExcepti
on
+ FullyQualifiedErrorId :
PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
_________________________________________________________________________________

If Jim was talking about the temp folder here:

Users\[Your Username]\AppData\Local\Temp

I regularly clean it the same way that I do the temp folder in the
Windows folder.

Well, you're not supposed to run anything in Powershell, now are you :-)

I just ran the command in a regular command prompt window and it worked
fine. Maybe MS fakes being unable to find the temp folder when
Powershell is used. I don't know.

%temp% can be parsed by the Command Prompt shell.
That does not mean Powershell will accept it.

Yes, that seems to be the case.

After a web page filled with suggestions didn't work
for Powershell, I tried this:

echo $env:temp

See if that works.

That shows the folder but it doesn't list its contents.

Or you could try

cd $env:temp

Changes folders to the temp folder but again, doesn't list the contents. However, a list of the contents was never the goal

Thanks for the info, Paul.

--
John C.

Take back Microsoft from India.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 25/02/28 09:39 AM, VanguardLH wrote:

"John C." <r9jmg0@yahoo.com> wrote:

When I run “dir %TEMP%” in Powershell, I get:

dir : Cannot find path 'C:\WINDOWS\system32\%TEMP%' because it does not
exist.

As a script interpreter, Powershell uses its own command set, like Get-Children, instead of the DOS commands in the DOS command interpreter (cmd.exe), like dir. Powershell does have some aliases on DOS commands,
like dir. Powershell isn't a more robust command interpreter. It is a script processor that is tied into .NET [Framework].

https://en.wikipedia.org/wiki/PowerShell

While Powershell and cmd both use console windows to load command shells
in which to execute inputted commands and display stdout, they are very different animals: one is a domestic cat that runs from dogs while the
other is a jaguar that will take on crocodiles. I've had little use for Powershell other than occasionally to do a command that is not available
in cmd.exe, run scripts that would never be possible in batch scripts
using cmd.exe, or to exercise system functions that are obtuse or
missing from other system utilities.

As such, Powershell operates differently on DOS environment variables.
For example, instead of using the DOS command 'set varname=varvalue", in Powershell you use $Env:varname = 'varvalue'.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.5

Unless you're willing to spend the effort and time to learn a new
scripting & system interpreter language, stay away from Powershell.
Learning it is tantamount to learning a new programming language, like
Perl, Javascript, Python, VBA, PHP, ,etc. Just use a DOS shell via
cmd.exe to run the commands and use the syntax to which you are
accustomed.

Load cmd.exe to open a console window in which the command shell
operates, and then issue your DOS commands. Stick with what you know,
or spend time learning Powershell which can take a very long time
considering how vast are its features since Powershell is built on .NET
CLR (Common Language Runtime) where all inputs and outputs are .NET
objects. I'm guessing you don't want to learn .NET nor Powershell.
Learning Powershell is on my to-do list, and I even have a wishlist of
books at my local public library on learning Powershell, but I never
manage to get the time nor motivation to delve much into it.

If you don't want to read books or online tutorials on Powershell to
learn it, go through all the tribulation of testing its use, and spend
time in forums or newsgroups trying to get help, you can find classes on Powershell. IT folks who are newsbies to Powershell take 2 weeks to
learn an intro to /some/ of Powershell, mostly to facilitate their
sysadmin tasks. Most impetus to learn Powershell is by those interested
in the realm of system administration. Of course, to newbies even DOS commands are a chore to learn, and then discover their anomalies.

Wow. Thanks for that, VanguardLH. Good info. The main reason I've been
using Powershell is because I'm able to copy and paste commands into it.
I still use the regular command prompt too though.

--
John C.

Take back Microsoft from India.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Mr Xi Ji Ping wrote:

John C. wrote:

When I run “dir %TEMP%” in Powershell, I get:

You don't run anything to search for the folder. You simply type
"%TEMP%" in the search box and the folder will open for you automatically.

Yes, that works all right. However, I created a shortcut to the folder a
long time ago.

Have you got a Search box in the taskbar or have you removed it because Indians were spying on you? Please advise.

I removed it because it was a huge, obnoxious waste of space. Since I
use OpenShell, I've got a more space-saving version of the search field
at the bottom of the Start Menu. And it works the same.

--
John C.

Take back Microsoft from India.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

John C. <r9jmg0@yahoo.com> wrote:
[...]

Wow. Thanks for that, VanguardLH. Good info. The main reason I've been
using Powershell is because I'm able to copy and paste commands into it.
I still use the regular command prompt too though.

You can also copy and paste in a Command Prompt window. Right-click
the upper-left icon, select Properties and on the Options tab tick the 'QuickEdit Mode' setting. You now can copy by selecting a piece of text
and pressing the 'enter' key. Paste is by right-click.

There's also 'Use Ctrl+Shift+C/V as Copy/Paste', but since the
'QuickEdit Mode' method exists since eons (XP? Vista?), I can't be
bothered to use more keys to do the same thing.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 3/2/2025 10:20 AM, Frank Slootweg wrote:

John C. <r9jmg0@yahoo.com> wrote:
[...]

Wow. Thanks for that, VanguardLH. Good info. The main reason I've been
using Powershell is because I'm able to copy and paste commands into it.
I still use the regular command prompt too though.

You can also copy and paste in a Command Prompt window. Right-click
the upper-left icon, select Properties and on the Options tab tick the 'QuickEdit Mode' setting. You now can copy by selecting a piece of text
and pressing the 'enter' key. Paste is by right-click.

There's also 'Use Ctrl+Shift+C/V as Copy/Paste', but since the
'QuickEdit Mode' method exists since eons (XP? Vista?), I can't be
bothered to use more keys to do the same thing.

There is also a scheme in the Terminal window consisting of:

1) Wipe over text to select.
2) Right-click one time, specifies "Copy"
3) Right-click a second time, specifies "Paste".

That's the basic idea at least, and that is pretty handy.

The Terminal (at least in Powershell) supports tab-completion
like it was "tcsh". You can type the beginning of an applet name
and tap the tab key, and for each tab press, it will cycle through
the matches it can find. It can also sometimes cycle through
parameters for a command, using the tab key.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Paul <nospam@needed.invalid> wrote:

On Sun, 3/2/2025 10:20 AM, Frank Slootweg wrote:

John C. <r9jmg0@yahoo.com> wrote:
[...]

Wow. Thanks for that, VanguardLH. Good info. The main reason I've been
using Powershell is because I'm able to copy and paste commands into it. >> I still use the regular command prompt too though.

You can also copy and paste in a Command Prompt window. Right-click
the upper-left icon, select Properties and on the Options tab tick the 'QuickEdit Mode' setting. You now can copy by selecting a piece of text
and pressing the 'enter' key. Paste is by right-click.

There's also 'Use Ctrl+Shift+C/V as Copy/Paste', but since the
'QuickEdit Mode' method exists since eons (XP? Vista?), I can't be
bothered to use more keys to do the same thing.

There is also a scheme in the Terminal window consisting of:

Does Windows 10 also have 'Windows Terminal'? (It came with 22H2 on
Windows 11. I'm on Windows 11.)

Anyway, my comments were for a 'Windows Console Host' window, running
cmd.exe aka 'Command Prompt'.

1) Wipe over text to select.
2) Right-click one time, specifies "Copy"
3) Right-click a second time, specifies "Paste".

That's the basic idea at least, and that is pretty handy.

Thanks for that! That also works for a 'Windows Console Host' window,
running cmd.exe.

So that gives at least three different ways to copy and paste in a
Command Prompt window.

[...]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

"John C." <r9jmg0@yahoo.com> wrote:

Wow. Thanks for that, VanguardLH. Good info. The main reason I've been
using Powershell is because I'm able to copy and paste commands into it.
I still use the regular command prompt too though.

Copy/paste is also in the shell for cmd.exe. After running cmd.exe to
see its console window, click in the top left corner of the titlebar
(where used to be the Control menu), or left-click on the titlebar, or
use Alt+Spacebar, to see its control menu. Select Properties, and look
under the Options tab. Ensure both QuickEdit and Ctrl keys options are enabled.

To check copy/paste is enabled, drag the mouse cursor over a line of
output in the console window to highlight it, and hit Ctrl+C to copy.
You'll hear a beep, and the highlighting disappears. In Notepad, or any
app with a clipboard interface, paste the newly copied text. In fact,
at the command prompt, hit Ctrl+V to paste inside the cmd.exe shell's
console window.

Frank also hit on the same method in his reply. As he mentioned, the
shell has had copy/paste for so long that I can't remember when it was
added. Using Google search with its time range criteria, I did a search
on "cmd.exe quickedit". Didn't get any hits until I used a timerange of 1/1/2005 to 1/1/2006. Possibly a different search would find earlier
hits. One hit was:

https://blog.codinghorror.com/stupid-command-prompt-tricks/

That guy was talking about Windows XP which was released in 2001. Looks
like QuickEdit has been around for 24 years, maybe longer.

Here are some videos on copy/paste in a command shell since reading instructions can sometimes be confusing.

https://www.youtube.com/watch?v=kISsbO0C0Gg https://www.youtube.com/watch?v=Xp-DOEii02c

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Frank Slootweg wrote:

John C. wrote:
[...]

Wow. Thanks for that, VanguardLH. Good info. The main reason I've been
using Powershell is because I'm able to copy and paste commands into it.
I still use the regular command prompt too though.

You can also copy and paste in a Command Prompt window. Right-click
the upper-left icon, select Properties and on the Options tab tick the 'QuickEdit Mode' setting. You now can copy by selecting a piece of text
and pressing the 'enter' key. Paste is by right-click.

There's also 'Use Ctrl+Shift+C/V as Copy/Paste', but since the
'QuickEdit Mode' method exists since eons (XP? Vista?), I can't be
bothered to use more keys to do the same thing.

Never would have found that. Thanks, Frank.

--
John C.

Take back Microsoft from India.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)