[QUOTE]\nWhich term it that?\n[/QUOTE]\n\nI didn't want to repeat it\n\nyou wrote 'windows xp version 5.1' <-\- and that's wrong !!\n\nThere's NT 5.1.\nNT 5.0 is win 2k\nNT 5.1 is Win xp\nNT 5.2 is 2k3\n\nBut NT 5.1 is not a version of XP. It is XP.\n\nNevertheless, somebody that KNOWINGLY writes what you also write you\nwrote "word for windows 6.0" <-\- that's really dumb. Somebody that\nwrites that is really beyond reason. I don't think you'll see out of\nyour tunnel. You don't have an organised mind. You mix things up and\nit means nothing to you.\n\n\ninfact, you also write\n"Word for Windows 6.0" . Now that's misleading, but I don't mind\nrepeating it 'cos the damage has already been done. In the days of\nwindows 3.1, secretaries were buying a dummy or idiot guide to\nwordperfect 5.2 I think it was an idiot guide. It was yellow, not\nblue. The book was titled something like. "WordPerfect for Windows\n5.2" But it was worse than that, 'cos it was for windows 3.1. It\ncaused a whole load of secretaries to think they were learning windows\n5.2 and wordperfect 3.1. I thought that misleading terminology was\nin the past, and even then, it was with wordperfect, not word.\nIt's Word 6 or 95 or 7 or 97 or 2000 or 2003. And which versions of\nwindows they work on is another matter. I think 2003 requires win xp\nsp2 or something.. Word 2000 will work in windows 98. They aren't\nstuck in a windows version, unless that particular version of office\nhas an issue.\n\n\n\n[QUOTE]\nIt still seems that there must be some way of getting WordPad to\nopen WordPad documents...[/QUOTE]\n\nIf this is just some odd issue, then your idea just doesn't follow..\n\nI'm willing to bet that wordpad does open wordpad documents, across\nwindows versions.\n\nFor example. THere was once an ugly as hell, greedy, ram eating\nprogramming IDE called jbuilder.. for writing java programs. (this\nwas before better ones like IDEA, or the more generic, Eclipse).\n\nI found that when putting the files onto a disk, it may have been an\niomega zip disk, or may have been a floppy disk. I can't remember. But\nit was a disk. And transferring the files to another computer. The\nfiles screwed up. When opening the jbuilder project, all the package\nnames were displayed in capital letters, and the program wouldn't\nrun. The only option within jbuilder was to rewrite bits of the\ncode..\nSomebody else had had exactly the same problem, years ago and asked in\na forum. He had had no reply. I emailed him and asked him if he had\nfound an answer. He said yes "transfer them over the network" that\nworks. Lo and behold, that worked.\n\nThis wasn't a standard issue. Almost nobody else had run into it. It\nwasn't an issue of - well, jbuilder should be able to do it. Because\ncomputers aren't like that. With standard problems, there are standard\nconvenient solutions or fixes. With non-standard problems, the\nworkarounds may not be convenient, things aren't so well documented.\n\nmoving data from one comp to another is a standard procedure. That\ndoesn't mean that any problem that occurs with that is a standard\nproblem.\n\nBut don't try to define this as a standard problem. Wordpad does open\nwordpad documents. But something ODD is happening along the way,\nduring the procedure, that is causing a problem.\n\nYou could do investigations to find out why. i.e. what is happening.\n\nOr you could just use a workaround.\n\nIf people here can reproduce the problem, then they may be able to\nsolve it.\nThe basis of solving a problem is reproducing it. (That's why\nintermittent problems are a nuisance). Maybe somebody has win98 or\nhas it on a virtual machine and is willing to look into it. Or give it\na try.. But it may work for them.\n\nYou have to realise that alot of things go on with computers. Problems\nare caused by very low level things. They aren't obvious. They have\nto be solved. Troubleshooting has to be done. In many cases, people\nhave done it before, seen the problem,. and can save you the\ntrouble. Posting to a newsgroup improves the chance of getting help\nthat way. I think you're looking at this wrongly.\n\nUse the workaround.\n\nand/or try to look into what is happening. And remember, if people\ncan't reproduce your problem then there isn't much they can do to\ntroubleshoot it on their own machine.\n\n i'd just consider the workaround as a solution. There are enough\nproblems. And there are interesting things to look into!\n\nIf you can be bothered you could look at the file in a hex editor on a\nsystem that can read it. And on one that can't. Maybe copy wordpad.exe\nfrom one machine to another.\n\nBut the way you're going about this isn't getting anywhere. It's\nalmost as bad as somebody I knew who stood for 5 minutes by a door and\nwhined "why is the door open", and that wasn't the first time they'd\nwhined about it.