2 years ago I installed a software package for a local Doctor who was using a Medical practice software suite that uses a stand-alone server and several users connected via a mapped drive to the 'serving' machine with simple file sharing and networking. The installation was relatively straight forward and easy to do--- share the root C drive on the 'server' then map a drive the 'server' root drive, then browse to the exectable just 1 folder inside the root and create a shortcut... in this case c:\MBACHI\MBAWIN.EXE

Once this was set you could plop the shortcut onto the desktop and run the program remotely. And change create alter files all day long. Printers too.

But today things are different and we 'upgraded' our machines to HT 3.0 GIG P4
Prescotts and at least a GIG DDR400 on GIG ethernet etc... oh ... did I mention WIndows XP Professional SP2? Thats the rub. It seems that the program no longer functions with Windows XP2 because of the internal protection the SP2 provides...

I can no longer set this system up using the previous methods however I can map drives browse the 'server' machine like crazy (yes go for the gig-ethernet folks its amazing)
however I have been unable to make this program connect and function like it used to.

I am attempting to install this same program on brand new XP PRO SP2 OEM software that supposedly allows programs to run through a LAN , thru a mapped drive, to the root folder of the stand alone 'server'. This is a peer to peer network running 1GIG CAT5E or 1000base-T with brand new machines claiming no hardware conflicts and/or problems in the event viewer or device mgr.

The Error message I get....

----------------------
DATA PATH NOT FOUND

(with an exlaimation point for pinnache`)
----------------------

Great NEWS --- isn't THAT wonderful?

So can someone please tell me how to effectively disable all the disabling new wonderful LAN features in WINXPPRO SP2?

Or if you you have other idearz (thanks Paul Sr.of Orange Cty Chopers for permission to use your likeness)

let me know!
SEAN

PS:list of atempted resolutions
- excepting the main program from firewall
- disabling the firewall
- shutting down DEP
- using static IPs
- PINGing ... works
- browsing works

but maybe not in correct order ... Idunno

Sean

U r fuct.... :-)

sharing the root of any "server" is a bad idea since you leave the entire system vulnerable.

Your first stop, before upgrading any OS, is to ask the question will what I am running work on the new OS? To get that answer you need to call the company of the package you are installing. Odds are you need the "upgrade" to work on XP.

XP doesn't have any "disabling new wonderful LAN features".

Clearly networking is working since you can map a drive so that is not the issue.

Data path not found usually indicates the program was expecting to find files, like on a cd but couldn't for some reason.

So start with basics. Logon as admin. Install the application locally. Does it install? Does it run? If it doesn't install on XP but does on 98, for example, that is the programs design. They don't want you running this on XP. Call them.

If it installs but doesn't run locally it can be a permissions issue. Usually you run into this issue when NOT logged in as admin but as a regular users. Check the programs documentation as to required file/folder rights for operation.

Thanks for the suggestions - especially the one about check to see if the software manufacturer's software will work with the OS in question. Nice. Good For You.

Been there, done that with them a month ago and they claimed - and here's no suprise - "yeah no problem". Too bad that the newer version of the same program actually does work on my network , however even on a 1 GIG Ethernet it runs like 3 legged moose. thanks to a new SQL setup parsing more than 4000 patient files.

Does the network actually function properly? Using a Gigabit Data Switch from D-Link and being just 10 yards away each system (of 4) recognizes the connection as such and a 20MB folder for example moves around in a virutal blink of the eye. The problem is I can not connect the old program thru XP PRO to do the same job with the orignal software which - oh by the way is 16 bit emulated in an NTVDM. Can ya Dig? The deal is that the newer version of XP PRO SP2 wont allow the previous version to run thanks (I believe) to all the wonderful anti-viri material in it.
But, can I be wrong?

Here's something in my corner: Just check out this dandy little article on MHIKROSHOFTZ website (name jumbled to prevent script kicking) to see how the SP2 patch is actually performing out there in the real world. The title of this dandy little article is called and I do quote:

"Some programs seem to stop working after you install WIndows XP Service Pack 2"'

Im not kidding. And it even mentions that file sharing is compromised with XPPROSP2. Isnt that somewhat important in small area networks?

Heres the article # ---> 842242
pop that into google or go directly to http://support.microsoft.com search for that article # and enjoy the juicy shizzle manizzle. Please take note, there are reams of functionality issues with the new release as it basically-(clasping the hands at the chin in wonderment} by sheer ACCIDENT - blocks the functionality of most LAN networking needs but very effectively kinda shoves ya towards server products or the dot-net structure quite well. Hmmmmmm ...I think Stewey from the Family Guy wrote the code for the pack. Any takers on that bet?

< I used the actual number instead of a link so that you can always trace the article down even after they move it around to hide the reality of their 'patch'. >

I'm hoping that someone else has already delt with LAN networking around the sp2 firewall and security features built into this new OS patch configuration and can provide me with an idea or two to confirm and/or try.

Again the problem is such that when I try to use the shortcut link to a main program folder, thru a mapped drive to the file server then to the network executable (in peer to peer environment) the program spits back with "Data path not found !" - despite the fact the mapped drive is seen by the OS , is visable in the 'my network places' and I can browse the main pc hard drive thru the network quite well thru that mapped drive letter of say 'Q'. This is how the previous version of the program would work and has worked for years. I am not trying to do this on the newer version whihc has a different setup method, I am simply attempting to run the old program the old way on new machines and it simply spits up on me.

The program is kinda odd in that it uses folders with patient data in them like \a and \b and \c with 190 patients in them up to letter \v and beyond if needed and a couple of other folders like \mbachi \mbawin \mbanote \wintime \WP The program can be completely backed up by just copying these folders and burning to a disk. To rebuild the program you paste the saved contents to a root drive and run the main program setup to rebuild. For as odd as it has been, it does work on XP PRO (no pack) with no trouble at the office now. We are just looking to enhance the speed of the network with the new gear that we bought but the newer version of XP PRO SP2 has set up a hurdle.

Is it the permissions? Do I need to add the guest account to the ADMINs? Do I have to set a special account for access and grant permissions to each folder in use by the program? Do i have to manually open ports in a peer to peer netwrok now? Is it the DEM feature inside windows now( look it up ;) )

Someone throw me a bone here....

In the meantime I will reinstall the software as perhaps it just didnt take the first time..."when in doubt ..punt."

If you would like to learn more about the potential jams that await you on this latest version of XP PRO SP2 ...please check out these articles and of course by all means g f y.

www.michna.com/kb/WxSP2.htm

XP is otherwise a solid OS, I just believe they went to an overkill level on the firewall settings as they are trying to plug the virtual swiss cheese of a explorer/browser they have been using till now.

BTW - MHICKROSHOFT must be aware of the issues and have since set up a chat site so that you can work with a systems engineer on your problem - that is - as long as you have a .net passport set up. =D HHmmmm, funny how that works.
Wink wink, nod, nod, know what I mean say no more.
call 1-888-SP2-HELP for more info. Again -
Honest Abe - if I'm lyin I'm dyin!

Id call em but Im interested in the forum's posts
first. IF nothing else, you will gain from my pain.

Sean

Done and done...

The minor differences in XPRPOSP2 and previous versions of it are enough to confuse the program setup and the installer himself - me - into thinking I'm mapping a drive correctly when in fact one will need to dig INTO network neighborhood from the lefthand side of the tasks (which are disabled by default upon install -thanks Bill and the gang), past the primary viewed resources, click onto the local area workgroup in this case, then the PC that hoilds the data, find the root drive share, dig in, then map that drive then create your short cut through the drive mapped.

I found that it does help transfers to shut off the firewall or create an exception for your program to allow for a more free flow of info as the program passes data from one firewalled install of XP to another..as it should.

But all of you who read this should make yourselves familiar with the SP2 update - its different and could possibly treat your programs as if they were viri - possibly causing you serious difficulty.

Sean