Execution of the following cmd file will cause my WinXP

SP2 PCs to immediately crash and restart:



:Start

NET USE (driveletter): \\(server)\(share)

NET USE (driveletter): \\(server)\(share)

:Finish



Where

"driveletter" = any available drive letter

"server" = any available server

"share" = any available share



---

Yes, the cmd file is trying to run the NET USE command

twice!!  This is evidently what triggers the crash - when

the PC is trying to map a drive that's already mapped.







Brian Steele

I just tried this twice and I do not repro. I map the drives with out error.

What happens if you disable your AV as a test?



--

Warren [MSFT]



This posting is provided "AS IS" with no warranties, and confers no rights



"Brian Steele" <steele_b@spiceisle.com> wrote in message

news:9f0a01c486ee$9ee6a2b0$a501280a@phx.gbl...

> Execution of the following cmd file will cause my WinXP

> SP2 PCs to immediately crash and restart:

>

> :Start

>  NET USE (driveletter): \\(server)\(share)

>  NET USE (driveletter): \\(server)\(share)

> :Finish

>

> Where

> "driveletter" = any available drive letter

> "server" = any available server

> "share" = any available share

>

> ---

> Yes, the cmd file is trying to run the NET USE command

> twice!!  This is evidently what triggers the crash - when

> the PC is trying to map a drive that's already mapped.

>

>

>

> Brian Steele

>

If the the AV disabled, the PC does not crash.



Unfortunately, disabling the AV on the PC in a networked

environment like ours is simply not an option.



It's a bit interesting though that's it's now possible to

crash WinXP by doing something as simple as this.  I

expected better "crash-resistant" behaviour from WinXP

after the SP2 upgrade.





Brian Steele







>-----Original Message-----

>I just tried this twice and I do not repro. I map the

drives with out error.

>What happens if you disable your AV as a test?

>

>--

>Warren [MSFT]

>

>This posting is provided "AS IS" with no warranties, and

confers no rights[vbcol=seagreen]

>

>"Brian Steele" <steele_b@spiceisle.com> wrote in message

>news:9f0a01c486ee$9ee6a2b0$a501280a@phx.gbl... 

when 

>

>

>.

>

We are experiancing the same issue with Trend OfficeScan. It occurs with both officescan ver 5.5 and 6.5. The BSOD only happens if you are using "net use" to map a share to a letter that is already in use. If you delete the mapping first "Net use driverletter: /delete" the crash does not happen. I have an open ticket with Trend on this but have not received a fix yet.



One other note. I have been able to build a brand new XP system, upgrade to SP2 and install Trend. On the fresh build the crash doesnt occur. The downside is there is no way we are rebuilding everyones systems just to upgrade to SP2!

I forgot to mention I have also been able to cause the BSOD using VBS scripts which do not explicitly call "net use" for drive mapping. It will crash the system if the drive letter is already mapped also.

 


	
Quote:
	

	

		

			
				Originally posted by FoyThompson 

We are experiancing the same issue with Trend OfficeScan. It occurs with both officescan ver 5.5 and 6.5. The BSOD only happens if you are using "net use" to map a share to a letter that is already in use. If you delete the mapping first "Net use driverletter: /delete" the crash does not happen. I have an open ticket with Trend on this but have not received a fix yet.



One other note. I have been able to build a brand new XP system, upgrade to SP2 and install Trend. On the fresh build the crash doesnt occur. The downside is there is no way we are rebuilding everyones systems just to upgrade to SP2! 
			
		
	
	

Very interesting.  I'm having the same problem.  I sent a request to Trend

also.  Great trouble shooting!  Have you tried manualy mapping a drive?



"FoyThompson" wrote:



>

> I forgot to mention I have also been able to cause the BSOD using VBS

> scripts which do not explicitly call "net use" for drive mapping. It

> will crash the system if the drive letter is already mapped also.

>

> FoyThompson wrote: 

>

>

>

> --

> FoyThompson

> ------------------------------------------------------------------------

> Posted via http://www.mcse.ms

> ------------------------------------------------------------------------

> View this thread: http://www.mcse.ms/message977119.html

>

>