[Freedos-user] Network problem with freebasic and freedos
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
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. regards Ulrich 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 signature.asc Description: Message signed with OpenPGP using GPGMail -- 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
Re: [Freedos-user] Keyboard issue
Hi, Eric Auer wrote: The ACPI throttle FDAPM SPEEDn thing? Which n value? I was using FDAPM SPEED1, in order to drop CPU speed from 1000 MHz to under 200 MHz to prevent the Borland runtime 200 bug. Bret Johnson wrote: Just as another troubleshooting item, does it happen even when you don't have a special keyboard driver loaded (like MKEYB)? That is, does it happen with just the default (BIOS) keyboard driver? If so, (or perhaps even if not so), you might try the MS KEYB program. It completely replaces the BIOS keyboard driver. I'll try that. Tom Ehlert wrote: that gives us the idea to ask: is this a PS/2 or USB keyboard ? It is a PS/2 keyboard. in fact, when running MKEYB, your system should behave (for these keys) almost exactly like 'no driver loaded', as MKEYB looks at these keys, and decides *very quickly* that it is not interested in handling these keys and passes control back to the BIOS. so I would guess that when this effect happens with MKEYB, it will happen with the default BIOS keyboard as well. So I'll do some testing with MKEYB too. Thanks to all :-) Marcos -- Marcos Fávero Florence de Barros Campinas, Brazil -- 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