Hi !
Thank you for your reply :)
there's no problem if you work in FreeDOS with the same file on the
network share X:. You just cannot open this file correctly with your
freebasic program
Yes i not have problem when i work with FreeDos and when i use my program for
... edit content file OR just copy there is a problem
All is correct ! i not have this problem when i use Dr-DOS or MS-DOS... it's
strange
This is contents :
=== Content of FDCONFIG.SYS :
DEVICE=C:\cpcdos\pilotes\dos\himemx.exe
SHELLHIGH=\COMFREE.COM /E:10240 /P=C:\FDAUTO.BAT
LASTDRIVE=z
DEVICE=C:\CPCDOS\PILOTES\DOS\IFSHLP.SYS
DEVICE=C:\CPCDOS\PILOTES\DOS\XMSDSK.EXE
rem DEVICE=C:\Cpcdos\pilotes\DOS\SMARTDRV.EXE /DOUBLE_BUFFER
=
=== Content of FDAUTO.BAT :==
SET LECTEUR=C:\
SET
PATH=%PATH%;%LECTEUR%CPCDOS\PILOTES\DOS;%LECTEUR%CPCDOS\SYSTEME;%LECTEUR%CPCDOS\PILOTES\RESEAU
KEYBFR
XMSDSK 102400 /y
==
=== Content of PROTOCOL.INI :
[network.setup]
version=0x3110
netcard=nic,1,NIC,1
transport=tcpip,TCPIP
lana0=NIC,1,tcpip
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP
[NIC]
DriverName=SIS190$
; This file gets inserted in to the driver's protocol.ini file.
; You can set hardcode lines for setting duplex/speed here.
[tcpip]
NBSessions=3
DEFAULTGATEWAY0 = 192 168 1 1
SUBNETMASK0 = 255 255 255 0
IPADDRESS0 = 192 168 1 11
DisableDHCP = 1
DriverName=TCPIP$
BINDINGS=NIC
LANABASE=0
TCPSEGMENTSIZE=1450
TCPWINDOWSIZE=4350
WINS_SERVER0 = 192 168 1 1
[PKTDRV]
DriverName=PKTDRV$
Bindings=NIC
intvec=0x60
chainvec=0x66
=
=== Content of SYSTEM.INI : ==
[network]
filesharing=yes
printsharing=yes
autologon=yes
computername = CPCDOS
lanroot = C:\cpcdos\pilotes\reseau
username=CPCDOS
workgroup = WORKGROUP
reconnect=no
dospophotkey=N
lmlogon=1
logondomain = WORKGROUP
preferredredir = Basic
autostart=basic
maxconnections=8
sizworkbuf=1498
[network drivers]
netcard = SIS190.DOS
transport = tcpdrv.dos,nemm.dos
devdir = C:\cpcdos\pilotes\reseau
LoadRMDrivers=yes
[386enh]
TimerCriticalSection=5000
UniqueDosPSP=TRUE
PSPIncrement=2
[Password Lists]
*Shares=C:\CPCDOS\PILOTES\RESEAU\Share000.PWL
CPCDOS=C:\CPCDOS\PILOTES\RESEAU\CPCDOS.PWL
==
From: uhan...@mainz-online.de
Date: Sun, 11 May 2014 03:58:48 +0200
To: freedos-user@lists.sourceforge.net
Subject: Re: [Freedos-user] Network problem with freebasic and freedos
Hi Sébastien,
I tend to forget these things but it may help to see your fdconfig.sys,
autoexec.bat, protocol.ini and system.ini.
If I understand you correctly, there's no problem if you work in FreeDOS with
the same file on the network share X:. You just cannot open this file correctly
with your freebasic program. I am not a developer so I can only guess: Do you
use any cache or buffer? Are the quotation marks correct? Can you still access
the file with your program? Would it be possible for your freebasic program to
copy the file to a temporary local folder, open it there, edit, save it, move
it back to x:. Maybe that's just crappy, but would it work?
Just a thought at 4 am.
freedos-devel might be a better place for this problem anyway.
regardsUlrich
Am 11.05.2014 um 01:04 schrieb Sébastien FAVIER
sebastien.ordinat...@hotmail.fr:I posted my problem in FreeBasic forum but
the problem is not of FreeBasic but FreeDos
can you please read the thread
:http://www.freebasic.net/forum/viewtopic.php?f=4t=22469
Thank
== Thread ==
Hi
I have a big problem
I have freedos with MSClient 3.0 installed and a network drive connected (x:)
With EDIT.COM I can edit files content on x: (no problem!)
but on my dos freebasic program (.Exe) can see files on x: but i can't read
content or write ! :(
I not have this problem with MSDOS 6 or 7 or DR-DOS, why?
can you help me please?
Thank's
===
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
#149; 3 signs your SCM is hindering your productivity
#149; Requirements for releasing software faster
#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
