Winrunner's M_ROOT not defined

[bizzzzzare]

Hi Elan,

I suppose you are looking for the file in the wrong place. Could you please check out at the location -

C:\Documents and Settings\UserID\Local Settings\Temp\

Else I would suggest do a file search. Incase still you are not able to locate it, another process could be to retrieve the contents of the file using a batch file. It could somewhat be like this in .bat file -

cd \
echo %username%
notepad.exe c:\DOCUME~1\%username%\LOCALS~1\Temp\wrstderr
pause

This would retrieve the contents to a notepad file.

Since you are saying that the script is being executed as a standalone from WinRunner alone, it seems the problem is only with cmd prompt execution of WR files. We would need to know the error message in the wrstderr file and only then decide the reason behind the problem...

Cheers....

Bizzzzzare

[elansamy]

I think my machine has a different configuration...becaz I don't have a Local Settings folder under my userid...

I restarted the machin and now its having a wrstderrr file directly in C:\ drive...

the error msg i saw in this file is: "wrun: Unknown option on the command line: \arch\wrun.exe"..

But this path has wrun.exe file in there...

Also I don't see c:\Windows folder either and so I am not sure where the .ini file is located...when I did a search for this file..I see two .ini files but located under different folders..IS it find that If I change the M_ROOT path in both the files and try again...

Hi Elan,

I suppose you are looking for the file in the wrong place. Could you please check out at the location -

C:\Documents and Settings\UserID\Local Settings\Temp\

Else I would suggest do a file search. Incase still you are not able to locate it, another process could be to retrieve the contents of the file using a batch file. It could somewhat be like this in .bat file -

cd \
echo %username%
notepad.exe c:\DOCUME~1\%username%\LOCALS~1\Temp\wrstderr
pause

This would retrieve the contents to a notepad file.

Since you are saying that the script is being executed as a standalone from WinRunner alone, it seems the problem is only with cmd prompt execution of WR files. We would need to know the error message in the wrstderr file and only then decide the reason behind the problem...

Cheers....

Bizzzzzare