Is ist a bug ?

I have a problem with a FOXPRO 2.6-Program on a Samba 3.0-Server.  
All programs (* exe, etc..)  are found and can be startet. 
They are found also, if the file names are written in lowercase.  
The FOXPRO program is started with the following line within a batch-program.  

foxr pc.app +x 

The following error occurs when foxr.exe is startet without any parameters:
"the indicated FoxProVersion was not found" 

So the FoxProLoader-program could not find its libraryfiles:  

foxd2600.esl foxd2600.eso foxdx260.esl 

These files could be found with Samba 2.2.8 but not with Sambo 3.0, 
because they are in lowercase.  
------------------------------------------------------------------------------  

Configuration:  
At present 2 LinuxServer with SuseLinux 9.0 and Samba 2.2.8   
One of it as backup-servers. Here the smb.conf:  

[global]
   os level = 20
   wins support = no
   domain master = no
   local master = no
   preferred master = auto
   
   security = share
   time server = yes
   load printers = yes
   hosts allow = 127. 192.168.0. EXCEPT 192.168.0.1
   encrypt passwords = yes
   printing = cups
   printcap = cups
   interfaces = eth0
   
   socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY
   netbios name = SAMBA
   server string = %v
   domain logons = no

   
   workgroup = WORKGROUP
   oplocks = no
   level2 oplocks = no
   lock spin count = 100
   lock spin time = 15
   dos file times = yes
   
[user]
   comment = Hauptverzeichnis
   path = /usr/local/samba/user
   read only = No
   guest ok = yes
   browseable = yes
   printable = no
	

Parallel I installed a Samba 3.0-Server, which likewise works at present in the 
SHARE mode.  
Before a few months I installed first Debian Linux "sarge" with new Samba 3.0.  
The program could be started problem-free.  
After an update of the system by InterNet the program could not be started any 
longer.  
First I thought of a system or a configuration error.  
To the conclusion I again installed the server with SuseLinux 9.3 and Samba 
3.0.13-1.1.  

[global]
	netbios name = server3
	workgroup = WORKGROUP
	socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY
	printing = cups
	encrypt passwords = yes
	oplocks = no
	level2 oplocks = no
	lock spin count = 100
	lock spin time = 15
	dos file times = yes
        store dos attributes = yes	

	security = share
	hosts allow = 127. 192.168.0. EXCEPT 192.168.0.1

[user]
        writeable =yes
	path = /usr/local/samba/user
	comment = Hauptverzeichnis
	public = yes

   

With this 3.0-smb.conf the program could not be started.  
I tested different parameters in this way:
- deletion of all files in the SHARE listing 
- new copy of th the files   
---------------------------------------------------------------------------

Finally I controlled all CASE-parameters with:

testparm -s  | grep case 

with the following result for Suse 9.0 Samba 2.2.8 and Suse 9.3 Samba 3.0 

default case = lower
case sensitive = no
preserve case = yes
short preserve case = yes

Then I changed this parameters in Samba 3.0:

default case = UPPER 
preserve case = NO 

thereafter all newly copied files where UPPERCASE and
the foxr.exe found its files and started.  

--------------------------------------------------------------------------------
------  

Question:  

Whats new?  

Why doesn't Samba 3,0 find the Foxpro files despite "case sensitive = NO", 
if they are written lowercase?  

--------------------------------------------------------------------------------
-------  

Thank you
Uwe Niemeyer