The TEMP variables point to...
TEMP=C:\DOCUME~1\Owner\LOCALS~1\Temp
TMP=C:\DOCUME~1\Owner\LOCALS~1\Temp
And it shows you are logged on as user; owner.
I am wary about the following...
TOOLPATH=/c:\Program%20Files\HP\HP%20Software%20Update\install.htm
UPDATEDIR=C:\DOCUME~1\Owner\LOCALS~1\Temp\radF7038.tmp
I don't understand why the TOOLPATH doesn't point to a path but to a HTML file and UPDATEDIR
points to the file 'radF7038.tmp' rather than a directory.
I really don't know :-(
When did all this start happening ?
--
Dave
| Oh, easier than I thought.....
|
| ALLUSERSPROFILE=C:\Documents and Settings\All Users
| APPDATA=C:\Documents and Settings\Owner\Application Data
| CLIENTNAME=Console
| COLLECTIONID=COL5123
| CommonProgramFiles=C:\Program Files\Common Files
| COMPUTERNAME=YOUR-XB2X7J77GN
| ComSpec=C:\WINDOWS\system32\cmd.exe
| FP_NO_HOST_CHECK=NO
| HMSERVER=
https://h30083.www3.hp.com/wuss/servlet/WUSSServlet
| HOMEDRIVE=C:
| HOMEPATH=\Documents and Settings\Owner
| ITEMID=dj-17724-8
| LANG=1033
| LOGONSERVER=\\YOUR-XB2X7J77GN
| NUMBER_OF_PROCESSORS=1
| OS=Windows_NT
| OSVER=winXPH
| Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Python22;C:\Program
Files\PC-Doctor for Windows\services
| PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
| PROCESSOR_ARCHITECTURE=x86
| PROCESSOR_IDENTIFIER=x86 Family 6 Model 10 Stepping 0, AuthenticAMD
| PROCESSOR_LEVEL=6
| PROCESSOR_REVISION=0a00
| ProgramFiles=C:\Program Files
| PROMPT=$P$G
| SESSIONID=1089242138233wuws04-l19ec4ed:fdcb9f9f95:540f
| SESSIONNAME=Console
| SWUTVER=1.0.22.20030804
| SystemDrive=C:
| SystemRoot=C:\WINDOWS
| TEMP=C:\DOCUME~1\Owner\LOCALS~1\Temp
| TIMEOUT=0
| TMP=C:\DOCUME~1\Owner\LOCALS~1\Temp
| TOOLPATH=/c:\Program%20Files\HP\HP%20Software%20Update\install.htm
| UPDATEDIR=C:\DOCUME~1\Owner\LOCALS~1\Temp\radF7038.tmp
| USERDOMAIN=YOUR-XB2X7J77GN
| USERNAME=Owner
| USERPROFILE=C:\Documents and Settings\Owner
| Veo_532_INF_PATH=C:\WINDOWS\INF\oem103.inf
| Veo_532_INSTALL_DIR=C:\Program Files\Veo Connect\Driver
| Veo_532_PNF_PATH=C:\WINDOWS\INF\oem103.pnf
| Veo_532_PRODUCT_VER=1.1.0.0
| VERSION=3.0.1
| windir=C:\WINDOWS
| __COMPAT_LAYER=EnableNXShowUI
|
|
| "David H. Lipman" wrote:
|
| > Look in the root of drive "C:" for the file SET.TXT !
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | I typed it in "set >c:\set.txt" exactly as you said and nothing happened. I
| > | got the same command prompt line "C:\Documents and Setting\Owner>" right
| > | after hitting enter. Thanks.
| > |
| > |
| > | "David H. Lipman" wrote:
| > |
| > | > Open a Command Prompt and type...
| > | >
| > | > set >c:\set.txt
| > | >
| > | > Open c:\set.txt in Notepad and copy the contents to the Clipboard.
| > | >
| > | > Please paste the information in your reply.
| > | >
| > | > --
| > | > Dave
| > | >
| > | >
| > | >
| > | >
| > | > | > | > | Hi,
| > | > | Been reviewing other posts that have 16 bit subsystem problems and have yet
| > | > | to find a post with my message. Here it is in a the box that pops up
| > | > | entitled "Windows 16 bit Subsystem"
| > | > |
| > | > | C:\DOCUME~1\Owner\LOCALS~1\Temp\. A temporary file needed for initialization
| > | > | could not be created or could not be written to. Make sure that the
| > | > | directory path exists, and disk space is available. Choose 'Close' to
| > | > | terminate the application.
| > | > |
| > | > | Can't run or install any older programs, which is doubly painful since I
| > | > | have an older printer that won't run now. Appreciate any help/suggestions.
| > | > | --
| > | > | Paul
| > | >
| > | >
| > | >
| >
| >
| >
