ISO 9001

 

Audio/video Tour Part 1

 

Audio/video Tour Part 2

 

Add me to the mailing list

 

 

 

 
Technical support
 
 
Problem with Windows XP service pack 2 (SP2)

 

Here is a transcript of an email correspondence which should help you solve problems with Windows XP SP2.

If none of the suggestions work, please contact us.


From: Richard B XXXXXXX [mailto:Richard.B.XXXXXXX@XXX.XXXX.com]
Sent: 04 November 2004 12:58
To: Peter Matthews
Subject: Pore-Cor Token Install Error


Peter:

I ran into a problem with installing Pore-Cor Beta version 5.01 on
my home computer. I had no problem installing it on my maching at work which runs Windows 98 Second Edition OS. However since I can't seem to spend much time on the software at work I decided to load it on my home machine. I had no trouble transferring the token back onto the floppy disk. My home computer runs Windows XP Home Edition with service pack 2 installed. Program loaded fine off the CD, but the transfer program would not transfer the token. When I tried I'd get a 16 bit window subsystem error:
C:\Documen~1\Rick\locals~1\Temp\CCMV32AA.exe
C:\Windows\System\Autoexec.NT The system file is not suitable for using MS-DOS and Microsoft Windows application. Choose close to terminate.
A couple of other error messages that came up after were: Pore-Cor Research Suites Security Problem Error code -1017 Process failed to terminate and the error code: Copy protection failed error code -1. I brought the floppy disk back into work this morning and successfully transferred the token back onto my work computer.

Any thoughts on how to get the token to transfer properly. I would like to work on my home computer not only from the time standpoint, but it's also a lot faster than my work computer.

Regards,

Rick


From: Peter Matthews
Sent: 09 November 2004 11:47
To: 'Richard B XXXXXXX'
Cc: deborah holtham; john price; Giuliano Laudone; tamsin page
Subject: RE: Pore-Cor Token Install Error

Hi Richard - sorry about the delay in reply, but I have been busy compiling version 5.02. However, that will not help you here, as this is a problem with the token transfer software, which we buy in rather than writing ourselves. I will therefore forward this to them, and get back to you when they reply.
All the best,
Peter


From "Peter Matthews"

To Richard BXXXXXXX/CL/XxXXXX@XxXXXX
11/09/04 08:05 AM

Subject FW: Pore-Cor Token Install Error

Richard - here's the fix. Peter.


The problem is that this file

C:\Windows\System\Autoexec.NT

which is part of the operating system has been deleted or corrupted. There have been instances of this happening with SP2 is installed on Windows XP.
The solution is to create a file with this name in the location given containing a single space character - you can use notepad to do this.
You may also have to create a file called config.nt in the same directory as they both tend to get broken at once.


To "Peter Matthews"

Subject Re: FW: Pore-Cor Token Install Error
Peter:

Thanks for the fix. I'll give it a try tonight and let you know the outcome tomorrow.

Rick


From: Richard B XXXXXXX [mailto:Richard.B.XXXXXXX@XXX.XXXX.com]
Sent: 10 November 2004 12:32
To: Peter Matthews
Subject: Fw: Pore-Cor Token Install Error

Peter:

The suggested fix did allow me to load the token onto my system, although I also had to add the files into the System32 folder as well (only autoexec.nt). However when I try to start the program I get the following System Error: The WIN16 subsystem was unable to enter protected mode, DOSX.EXE must be in your autoexec.nt and present in your path. I didn't get the chance to try it, but I'm wondering if I should reinstall the software off the CD. Don't know if this is something the installer program does or not.

Rick


From: Peter Matthews [mailto:P.Matthews@plymouth.ac.uk]
Sent: 10 November 2004 14:07
To: Richard B XXXXXXX; mark@xxxxxxxx.co.uk
Subject: RE: Pore-Cor Token Install Error

Mark - any more thoughts on this ? Not something we have ever encountered with our software before, so I think it is still something in your bit.
Many thanks,
Peter.


Peter

The solution I gave was the 'quick fix' which has always worked in the past. The more correct way is outlined in this

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

If they follow those instruction it will create those files in a complete form and the problem should be solved.

Regards
Mark

 

Support: see also Registration, Loading, Documentation (Application Notes, Help System, Publications), Support and Training, and Frequently Asked Questions.