Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Valery Sedletski

Pages: [1] 2 3 4
1
You need at least this:

Quote
[PROT_MAN]

   DRIVERNAME = PROTMAN$

[IBMLXCFG]

   nullndis_nif = nullndis.nif
   tcpip_nif = tcpip.nif

[tcpip_nif]

   DriverName = TCPIP$
   Bindings = nullndis_nif

[nullndis_nif]

     DriverName = NULLNDS$


in your protocol.ini. (Where NULLNDIS.OS2 is an example NIC driver, a NULL one) Maybe, you deleted protocol.ini?

2
Programming / Re: Get a Free copy of ArcaOS 5.0.1
« on: September 22, 2017, 12:28:15 am »
Why do you need this? Sound Blaster 16 (PNP) driver works fine. Also, you can try both High Definition Audio and AC97 emulation with Uniaud, one of them should work, if I correctly remember.

Ah, I understood. You want sound support for OS/2 host. Unfortunately, sound is not working under host OS/2, yet. But OS/2 guest running on any other host, works with sound. Sound support is quite an effort for me, as I didn't worked with sound applications, yet. Need to learn a bit, how to work with sound hardware.

PS: The VBox development is paused a bit, because now I am working on fat32.ifs. It will be continued soon. There are some problems with financing, though. Last time,  I was enhancing the shared folders IFS in the OS/2 guest additions. Will need to finish it first. Not sure yet, when I could work on sound support.

3
General Discussion / Re: Trying to get the forums back.
« on: September 19, 2017, 10:29:53 pm »
Logged in successfully, trying to post a message ;-)

4
Programming / Re: poll() and select()
« on: June 24, 2017, 12:10:55 am »
You could create a separate threads for polling each file descriptor, and posting a semaphore if ready. Then use DosWaitMuxWaitSem on a set of those semaphores, for example. Or, create your own select/poll implementation supporting files under the hood.

5
Programming / Re: poll() and select()
« on: June 23, 2017, 10:41:17 pm »
OS/2 implementation of select() supports sockets, only. Not files.

6
Storage / Re: About FAT32 and AN
« on: June 19, 2017, 03:29:59 am »
2Doug Bissett: Are you sure you installed fat32.ifs correctly? I changed nothing related to unicode, so filenames should be shown the same as in 0.9.13. The only change is the Unicode translate table loading is now located in uunifat.dll, and if it is not on the LIBPATH (or, an older ufat32.dll version is on the LIBPATH), the unicode to local codepage translation may not work. Also, all components versions are checked to be consistent, so if you have, for example, an older cachef32.exe, but newer uunifat.dll and fat32.ifs, then cachef32.exe will not load successfully, and unicode translate table will be not loaded. Are you sure it has been loaded? What does cachef32.exe write on start? Is there any errors?

7
Applications / Re: Establishing Wlan Connection by Command Line
« on: June 16, 2017, 02:20:18 pm »
What is the problem? You just create a config for wpa_supplicant.exe, start it, and additionally start the DHCP client (if needed)

8
Storage / Re: USB and Format Issues
« on: May 30, 2017, 02:19:04 pm »
2Eugene Gorbunoff: How could reformat help him? Does it create the LVM info?

Anyway,  using DFSee, as I suggested above, is non-destructive. It only writes a DLAT sector before the boot sector. After you eject and insert again the flash stick, it will be mountable, and no need to format. Using reformat formats the stick, so, its contents will be lost. What if it is other user's flash stick and he is not agree to reformat it?

9
Storage / Re: USB and Format Issues
« on: May 30, 2017, 01:56:25 pm »
2Paul Richards: If you able to see disk contents in DOS prompt, then in OS/2 command prompt it should be seen too. Did you assigned the LVM info to flash disk? If not, the disk will be inaccessible. You need to take DFSee from http://hobbes.nmsu.edu and assign a drive letter first.

10
Applications / Re: Avoiding Windows 7's CHKDSK?
« on: May 08, 2017, 07:39:42 pm »
2Andre Heldoorn: What program writes that message? Which version? Do you have U*.DLL on LIBPATH? Are there older UFAT32.DLL on the LIBPATH? Did you unpacked all correctly?

PS: the required directory structure is preserved in the .ZIP archive.

PPS:
> What program writes that message?

Ah, I see, it is cachef32.exe. It cannot find LoadTranslateTable function in UFAT32.DLL. So, either, or no U*.DLL on LIBPATH, or an older version of UFAT32.DLL is used. Please clean up your LIBPATH from dups. eCS usually puts UFAT32.DLL in \ecs\dll, and I usually put it in \os2\dll. So, it should be only one newer copy.

11
Applications / Re: Avoiding Windows 7's CHKDSK?
« on: May 06, 2017, 02:13:45 pm »
Dirty flag on FAT32 is the same as on FAT16 -- it is a bit set in the 1st FAT entry. On exFAT, though, it is set in the boot sector instead, but this is not the case.

12
Applications / Re: Avoiding Windows 7's CHKDSK?
« on: May 05, 2017, 12:52:20 pm »
For an old FAT16-based MP3 player, it is better to use new fat32.ifs with FAT16 support. The VFAT LFN's are now supported on FAT12/FAT16 too. So no need to use any REXX utilities to convert LFN's, or vfat2ea, it is all obsolete now. Please look at http://trac.netlabs.org/fat32/ for a download link.

And, it is possible that fat32.ifs will behave differently than the kernel FAT, so your error will be gone.

PS: The reserved bytes in directory entries which are used to store the EA's pointer by OS/2, are reused by M$ on FAT32 as a high word of a cluster number (because cluster number is 32-bit on FAT32). On FAT12/FAT16, these bytes are not used as cluster number is 12 or 16 bits, and no high word is needed. So, it should play no role.  And you say that the drive is considered *damaged*, not dirty by windoze, so I doubt it's something with unused bytes in dir entries. As I can see, the trash in dir entries does not prevent the disk to be mounted.

PPS: is it possible to upload the disk image somewhere? (I could suggest my ftp for upload, if so)

13
2Sigurd Fastenrath: The default kernel is 14.104a_UNI. But also SMP kernel and OS/4 kernel and debug are supplied too. Also, default loader is QSINIT, but you can choose IBM's or OS/4 loaders. -- These can be choosen in the boot menu. And the default and fail safe configuration is without SMP. But you can also choose to use a PSD (os2apic.psd/os4apic.psd/acpi.psd by Pasha/acpi.psd by David Azarevicz). Some components are optional and not supplied on the disk for legal issues. It's up to an user to add them manually, just by copying to needed directories. These components include ntfs.ifs, Panorama and ACPI. (Please read readme.eng how to add them yourself). You also can add many programs yourself, like Netdrive, RSJ CD writer, DFSee, Mesa2 etc. For that, you need to copy programs to \apps directory, add the path to its directory to paths.sed and add WPS objects creation .rc file to rc.cfg. There's a big collection of ready to use .rc-files supplied with the boot disk. BTW, I use much more programs on my own bootable flash disk. The official distribution is just limited in size and commercial programs are not included (but there are still some shareware and abandonware programs).

14
2Dave Yeo: No. It is universal multiboot compliant loader, like GRUB.  (but it is began from David Zimmerli stub of os2ldr reimplementation from EDM/2, called FreeLDR, and preserved this name). FreeLDR preloads a number of files to memory, in multiboot compliant format. Then OS/2 booter is started from it. OS/2 booter takes preloaded files from memory and creates special minifsd and microfsd, which retrieve preloaded files from memory and boots OS/2. Then minifsd passes control to specified IFS and booting continues as usual. So that, we can boot from different filesystems. FreeLDR preloads files to memory (in multiboot-compliant format) from supported filesystems and then boot process continues using an IFS. OS/2 booter (bootos2.mdl file) acts as universal microfsd/minifsd pair for different filesystems. So far, I successfully tested the following IFS'es: FAT32, hpfs, jfs, ext2-os2, vfat-os2, ramfs. The Live OS/2 boot disk uses ramfs ramdisk to boot from. The files are first preloaded to memory in multiboot-compliant format (as multiboot modules). Then ramfs disk is mounted, the files are copied to ramfs and boot process continues from there. So, it uses another method of ramdisk booting. In contrast with Veit's memdisk, I use an IFS-based ramdisk, and files are taken directly from the filesystem, no need for packing files to *.pk archives. But like memdisk, it uses the el-torito boot without floppy emulation. Also, as FreeLDR is GRUB-compatible, it can boot linux kernel via linux.mdl loader too. It can chainload bootsectors and DOS kernel or NTLDR via chain.mdl loader. It can boot L4 kernel via its own loader, and other multiboot-compliant kernels too. The multiboot support code and code for reading different filesystems is ported from GRUB. It should also serve as a microfsd for os2ldr, but it is broken atm. Multiboot support allows to boot different OS'es or different single OS configurations from a single menu, which is defined in a number of config files. For example, the Live OS/2 disk can boot: 1) FreeDOS from diskette image via memdisk (not Veit's memdisk, but Peter Anvin's memdisk taken from SysLinux) 2) memtest86, which is loaded via linux.mdl 3) three OS/2 configurations via bootos2.mdl: a) Tshell b) PM/WPS/Warpcenter c) PM/WPS/XWP.

PS: Originally, it is needed for osFree project, to boot L4 microkernel and to be more OS/2-like at the same time. osFree develops an L4-based OS/2 personality, so we needed the method of booting L4. L4 uses GRUB usually, but we wanted more OS/2-like boot with microfsd etc. And also it made universal enough to boot OS/2 too.

PPS: Also, it uses features ported from a fork of GRUB by Adam Lackorzynski (one of L4 Fiasco developers from Technical University of Dresden). These features (toggle command and GRUB variables support) allow to set boot options from main menu. You press a key and it toggles different values of a variable. Then variables are substituted into boot scripts. Also, these variables can be passed into config files via text preprocessor (like #define in C preprocessor does). For example, it can be passed to config.sys.  Also, the files like config.sys can contain directives like !include, !ifeq, !ifneq etc, so you can control different parameters passed to config.sys and include/cut pieces of config file depending on that. The idea to use text files preprocessor is used in Veit's os2csm too. But I use more human-readable format for text preprocessor directives. And Veit intercept's int 13h during config.sys reading. I just patch config.sys in memory after preloading it by freeldr.mdl.

PPPS: Also, FreeLDR can start from QSINIT/os4ldr menu on HPFS or JFS filesystems. (HPFS support is added into FreeLDR too, also it supports FAT, ext2, ntfs, JFS, ISO9660 and different UNIX filesystems, like reiserfs, XFS, UFS2, FFS etc).

15
2Dave Yeo: reverse-engineering? Why? It is open source. Source code is available from osFree svn: https://sourceforge.net/projects/osfree/, http://osfree.org. Maybe, you confused it with OS/4?

Pages: [1] 2 3 4