I've recently set up a new server running RH 6.1 and Samba 2.0.5a. All our older servers are running 1.9.18p10, and were left that way on the "If it ain't broke" principle. On the new server, I've noticed that DOS wildcards don't work correctly for some (but not all) old 16-bit DOS programs running under Win95/98. The symptom is that the program only "finds" the first file matching the wildcard spec. The WHATSNEW.txt file says that 2.0.5a contains a fix for a DOS wildcard bug, so I'm wondering if that fix fixed one thing and broke another. I did search the archive of this list, and was surprised to find no mention of this problem. Does anyone have any ideas? TIA... - Fred Viles <mailto:fv@epitools.com>
As a followup to my own post, I've installed 2.0.6 now and it has the same problem. I've compared testparm output between the 2.0.5a and 1.9.18p10 systems looking for config differences that might explain it. No luck. This is bugging me, since it breaks a couple of still very useful legacy DOS apps that I use frequently. Any advice would be much appreciated. | I've recently set up a new server running RH 6.1 and Samba 2.0.5a. All | our older servers are running 1.9.18p10, and were left that way on the | "If it ain't broke" principle. | | On the new server, I've noticed that DOS wildcards don't work | correctly for some (but not all) old 16-bit DOS programs running under | Win95/98. The symptom is that the program only "finds" the first file | matching the wildcard spec. | | The WHATSNEW.txt file says that 2.0.5a contains a fix for a DOS | wildcard bug, so I'm wondering if that fix fixed one thing and broke | another. | | I did search the archive of this list, and was surprised to find no | mention of this problem. Does anyone have any ideas? | | TIA... | | - Fred Viles <mailto:fv@epitools.com>
Hi, I had the same problem. Some Dos apps on W98 and W95 Dos-boxes found only the first file in a directory. I wrote to this mailing list some months ago, but nobody could reproduce the problem. I told it to SuSE. They reproduced it, and they said, it was fixed between 2.0.5 and 2.0.5a. I'm sure, they fixed a Dos wildcard problem, but it was not the problem I had. Not all Dos apps have this problem, most of them work fine, but a few do not. I found out, that setting nt smb support=no in smb.conf fixes the problem. During the last months, I did some updates, a new Netware client, vredir.vxd was updated, and W98 was updated to W98 II. On the W98 II PC, the problem is gone. On NT 4.0, the problem never existed. On W95, it is still there. Unfortunately I can't tell you, which of the updates on W98 made the problem disappear. But maybe it is the update to the second edition. On W95, I have vredir.vxd version 4.00.1120. On W98 II, I have vredir.vxd version 4.10.2222. But I'm not sure, if vredir.vxd causes the problem. Using Lanalyze, I tried to find a difference between Samba 1.9.18 and Samba 2.0.5a. If the Server runs Samba 1.9.18, and the client looks for *.*, Win 95 asks for files matching ????????.???. If the Server runs Samba 2.0.5a and no nt smb support parameter is set (default = yes), Win 95 asks the server for files matching >>>>>>>>">>>. But I don't know why. Solutions? Either, you use Win NT on your clients. Or you try to update to W98 II (but I'm not sure, if it helps). Or you set nt smb support=no in smb.conf. I hope this helps. -- Sent through Global Message Exchange - http://www.gmx.net