OS2user

>1) i don't have OS2 on my PC (at the moment....) - what version do you suggest? Well, the original Warp4 back from 1996 won't install any more on todays hardware with large HDDs right out of the box, without updating the boot diskettes (mainly kernel, loader, fdisk (boot manager), IBM1S506.add). Then it also is strongly recommended to update all components (main OS, drivers, LAN/Peer components, ) to the latest freely available levels. The right place to start looking for this and also find links to almost all important and relevant locations about OS/2 is: http://www.warpupdates.mynetcologne.de/deu...arpupdates.html The ideal solution would be, getting a hand on a Warp4 license and then upgrade to eCS 1.1 for $99 or somehow get a hand on MCP1 or MCP2 (see below). Btw. MCP2 also comes with eCS, it's part of the package. eCS (www.ecomstation.com) is an up-to-date and enhanced IBM OEM version of OS/2, which also includes free driver availability and available from Mensys.com in the NL, but also from lokal dealers. Trying to get the same from IBM requires an annual subscription, almost in the same range of buying eCS.. IBM also still is selling their current version of Warp4, called MCP2 (Merlin Convenience Pack V2, that's the one eCS is based on), but one has to be _very_ persistent, to be actually be able to get it from IBM, at least if you're not a really _big_ client ;-) For any additional questions, just visit the Usenet OS/2 and eCS relatet NGs and ask your questions there But one warning ahead: if you come across posts of a Tim Martin (he also uses some different aliases) just ignore them, he can't help it, but simply is a moron. 2.) Ah, I see. Most Pascal programmers on OS/2 are using Speedsoft's Sybil, AFAIK 3.) I assume that the Linux version also requires at least some of the modifications, that are desirable for OS/2 as well. So going from there for a possible OS/2 version might not be the worst idea. Regards OS2user

> good, so its not my fault :) Yep, seems like you're off the hook on this one ;-) >maybe i wont be able to release an OS2 port with the next release :( Don't sweat it. A couple of days/a few weeks more or less won't kill us ;-) What kind of compiler are you planning to use? IBM's VACC 3.5 (I'm not quite sure if the latest one was 3.4, 3.5 or 3.6), the latest OpenWatcom (free from Scitechsoft.com) or the current GCC (free from Innotek.de)? Do you expect that the compiler takes care of handling OS/2's EAs (enhanced attributes), long filenames and handling of files >2GB or would this most likely require more or less large code modifications? You probably already know about comp.os.os2.programmer(.misc), where most of the OS/2 developpers of current applications hang out. Don't hesitate to ask there, if you have any questions. Unfortunately I can't be of help here :-( regards OS2user

I just learned from an very talented OS/2 (low level) software developer, that DOSLFN won't work on OS/2 at all. If I understood him correctly, then the situation is like this: An OS/2 filesystem driver "knows" about the abilities of the requesting application and in the case of a DOS session, that means they are always only 8.3. One way to circumvent this, would be to start a DOS session, that doesn't use the DOS that comes with OS/2 , but to boot one from Floppy or a bootable image from HDD to avoid the use of OS/2's FSFilter.sys. But this would then limit HDD access to read only, since without this driver, partitions are write protected. And as soon as FSFilter.sys would additionally be loaded in that Doss session to obtain HDD write abilities, the OS/2 file system functions would be active again and we would be back to where we started. The reason why the CDRom and the Ramdisk still worked is, that they are net drives, which are not handled by DOSLFN. So without modifications by IBM to those file system drivers, we won't get LFN in Dos/Win3.1 sessions on OS/2. OS2user

I haven't tried that yet. > the D32 version uses W9x LFN APIs for file stuff maybe thats the problem I really don't know. In the meantime I also found and got the latest Volkov Commander and see the same thing happening there as well. So I also wrote to Henrik, hoping that he might have an answer from his view as the author of DosLFN. > additionally, i have never compiled/tested a OS2 port of the current version, if there are more people who would like to use NDN in OS2 i can try to compile and upload a OS2 port of the next release too?! This one then would have to compete with Brian Havards very popular FileCommander FC/2 ;-)) But it shurely would be nice, to have a possible additional alternative in a program, that is widely popular for Dos and still actively maintained..

I just found something else quite strange. When I load LH D:\UTIL\DOSLFN.com Version 0.32o (05/03, www.tu-chemnitz.de/~heha/hs_freeware/doslfn.zip) in Autoexec.bat, the only drives, where NDN is showing me files, are my Ramdisk and CD-Rom. A loaded DOSLFN apparently is also the reason why NDN for some reason, doesn't see the Temp directory on my H: drive. Without NDN loaded, all drives can be listet fine from the Dos command shell. Can somebody please explain to me what's going on?

I'm not quite sure yet, if this is the right place for my question, but anyway. I'm running OS2 Warp4 and for the first time, I try to use NDN_2.14_Bld4281_DPMI32_20040412 in its DOS box. NDN now is complaining all the time: Error! Could not create the directory H:\SysTEMP\TEMP\ This is the existing place, where both my TMP and TEMP variables set in Autoexec.bat, are pointing to, as do the ones set for OS/2 in Config.sys. Did I miss to set/modify some NDN settings or what's the matter?