PDA

View Full Version : Inability to install Data Import for NX-80V! Help!


rowver
08-22-2003, 01:08 PM
Hi,

Please be patient here. Before you tell me to read any other tread on this issue, please know that I have checked everything. They all don't work!

My problem is that the Export SW program has been installed, but there seems to be problem everytime I try to connect the NX-80V via the USB port through Data Import, it tells me that the NTMAP.SYS file is missing. I can't complete the connection.

This problem only happens when I try to connect via the Data Import SW for MS. It seems ok when I try it for CF cards.

I still have my T665 and using the Import SW seems fine. So it only appears to affect the MS mode of Import Data for my NX-80V.

Since I just got this, I am sure you would understand this really bothers me so much!

Has anyone encountered this? I have also tried to download the NTMAP.SYS file from the internet but it makes things worse actually!

I am desperate, if anyone knows about this and how to fix this, please let me know!

Unregistered
08-22-2003, 08:19 PM
Data Import is the app in ROM on the Clie.

Very Important, did you uninstall MS Export before installing Data Export on the desktop PC?

MS Export actually worked for me before I did anything, when I migrated fron the NX70.

I have no NTMAP.SYS file in Windows XP! Something is messed up and you didn't state what operating system your desktop PC is using.

Don't bother asking Sony, they'll have you reinstalling the whole desktop PC's OS.

n2ifp
08-22-2003, 08:21 PM
Sheesh, I go to the bathroom for a minute and get logged out!:mad:

rowver
08-22-2003, 10:22 PM
At first I did not. I then subsequently uninstalled everything and reinstalled for NX-80. The same problems come about. I really don't know what to do.

n2ifp
08-23-2003, 04:45 AM
Originally posted by rowver
At first I did not. I then subsequently uninstalled everything and reinstalled for NX-80. The same problems come about. I really don't know what to do.

That's the problem, no easy fix! The reason is there are still traces of the old driver and app on the desktop PC. It may require editing strings in the registry, deleting files in the various system folders, and elseware. That would go beyond the scope of this forum. Sony's recommendation would be to reinstall the PC's operating system.

You can try this first:


Uninstall Data Import, Reboot your PC!
Then reinstall the old MS Export, Reboot the PC!
Uninstall MS Export, Reboot the PC!
Install Data Export for the NX80.


Good Luck!

oyakodon
10-14-2003, 11:10 AM
Greetings! I have been having similar problems w/ my NX80, though I haven't been getting the NTMAP.SYS message. My error has been saying that it "cannot connect with computer" when I try using Data Import with the NX80, however my wife's NR70V's MS Import works just fine.

I've tried uninstalling and reinstalling Data Export as this thread has mentioned but it has failed each time. Just for kicks I uninstalled the Clie SCSI driver and succeeded in disabling my wife's MS Import as well! When I reinstalled Data Export it started working again.

So here's my theory, and I plan on trying it out when I get home: My Data Import works fine at work, and this is the first Clie I've ever had the USB Mass Storage driver installed for on this computer. My thought is that, whenever you're reinstalling Data Export, it's reinstalling your old driver that you had for your T665 (and similarly for our NR70). This may explain why our old Clies still can be read as a removable drive and the NX80 can't, assuming that the NX80 needs an updated driver.

My test for today will eventually be to uninstall the driver, rename it to something else, then try reinstalling Data Export again (or just try connecting via USB to see if it seeks a new driver and finds something else) and see if things connect at that point.

If anyone else has tried this already please let me know. I'd kinda hate to lose the NR70's ability to connect properly 'cause then my wife would kill me : ) . The driver reinstalled last time w/o a problem so hopefully it won't be an issue. And if I'm using the wrong driver name, please feel free to correct me.

Thanks and pardon my rather windy post,

Kevin