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 ... 19 20 [21] 22 23 ... 25
301
Hardware / Re: Preparing an USB Flash drive with FAT32 with DFSee
« on: November 19, 2017, 04:39:28 am »
> What is the correct name for this problem?  "Un-proper CHS layout on the disk?"

The problem is generally with missing LVM info. If no explicit LVM info on disk, it won't be mounted under OS/2, so, you should create it for OS/2 kernel to call MOUNT for IFS drivers. (To be exact, the kernel will call only in-kernel FAT driver to mount disks without explicit LVM info, which will fail. It won't call IFS'es FS_MOUNT routines). Un-proper CHS layout is another problem. It prevents to add the LVM info with LVM.EXE. But DFSee allow to do this with any disk geometry (so, you can avoid destroying partitions. If the flash stick is not your own, but your friends' or clients', then repartitioning is undesirable. But you can optionally do a repartition, if you want better compatibility with LVM.EXE and your BIOS, if you want it to be bootable)

302
Hardware / Re: Preparing an USB Flash drive with FAT32 with DFSee
« on: November 19, 2017, 03:16:41 am »
Unfortunately, if you'll try to use FORMAT frontend with an erased flash stick, you'll get the following:

Quote
[d:\var\log]format j: /fs:fat32 /v:spower
SYS1512: The requested function is not supported on this disk or
diskette for file system FAT32.

But

Quote
[d:\var\log]fat32fmt j: /fs:fat32 /v:spower
FAT32 version 0.10.r331 compiled on Nov 11 2017
The new type of file system is FAT32.
Диск не имеет метки тома.
Warning!  All data on hard disk j: will be lost!
Proceed with FORMAT (Y/N)? y
Size: 14336 MB 30282525 sectors.
512 Bytes Per Sector, Cluster size 8192 bytes.
The volume label is SPOWER.
The Volume Serial Number is 0CEA-3537.
32 Reserved Sectors, 14772 Sectors per FAT, 2 fats.
15140864 kilobytes total disk space.
15122432 kilobytes are available.
0 kilobytes are in bad blocks.

Formatting...

100% of the disk has been formatted.

Wrote 15151104 bytes in 7.06 seconds, 2.05 Megabytes/sec
Clearing out 29592 sectors for
Reserved sectors, fats and root cluster.
Initialising reserved sectors and FATs.
WARNING: failed to set the volume label, rc=26


Format completed successfully.


will succeed. So, you can try to format with a standalone FORMAT utility. The minor problem that it fails to set the volume label with DosSetFSInfo, because of ERROR_NON_DOS_DISK == 26 error. But you can try it again after FORMAT. The FORMAT.COM frontend fails to pass control to FAT32 format routine, unfortunately.

Note that big floppy flash disks have "Fake Disk" disk name, and "Fake volume" / "Fake partition" in the volume/partition name. That is the default LVM Info, which Lars is emulating on big floppies.

303
Hardware / Re: Preparing an USB Flash drive with FAT32 with DFSee
« on: November 19, 2017, 02:14:41 am »
2Martin: Yes, you should to switch the "Expert mode" on in newer versions of DFSee, unfortunately. I don't know why the author removed it in non-expert mode, because it is one of the most needed functions, at least, for me. If "File->open object to work with->Partition->" does not list the flash disk, this means that you deleted the partition on it, or your flash disk is big floppy. You should back up it and erase, and create a partition then.

> I'm also not sure where is the "add the LVM info" function on the DFsee UI.

It is called "Edit->Edit LVM Info" in newer versions of DFSee. It is near the "Edit partition tables", which is used very frequently, too. (Need to switch the Expert mode on, of course)

> About the "large floppy stick" how does one produce it? Does it depends on the hardware of the stick?

You want to create a big floppy? You should erase the beginning of the flash disk with zeroes with the

Quote
wipe "" 0 2048

command, then try formatting it. (But select the full disk first, if you don't want to occassionally erase the wrong disk!) Lars' version of USBMSD.ADD should emulate the MBR with partition table, and the LVM info. I'm not sure if DFSee will allow you to format a flash disk without a partition created, but you can try my FAT32.IFS format instead. Unfortunately, format of the flash stick without a partition may not work under OS/2. But you can erase it under OS/2 and format it under windows then.

2Pete: What is USBcfg for? Never used it.

304
Internet / Re: Torrent - what is actually working???
« on: November 16, 2017, 03:21:57 pm »
I used both QBitTorrent (it is newer and more powerful) and ACT (special coloured version of ctorrent, written by acw. Unfortunately, author is R.I.P. now, so no updates for his software anymore, unfortunately. But there is still his web page alive: https://sites.google.com/site/os2acw/ Maybe, ACT from this page will work, it should be the latest).

305
Hardware / Re: Preparing an USB Flash drive with FAT32 with DFSee
« on: November 13, 2017, 08:48:12 pm »
Also, the [micro/mini]SDXC flash cards (these are those larger than 32 GB) are usually formatted as exFAT on the factory. This is the cause some OS'es or devices cannot see such flash cards, because of an exFAT FS, unknown to them. Newer versions of fat32.ifs contain an experimental exFAT support, so you can see such flash cards in OS/2. But if your device does not see the exFAT filesystem, it is better to reformat it to FAT32. The disadvantage of FAT32 (compared to exFAT) is that files >= 4 GB are unsupported (because the file size field in directory entry is 32-bit, which limits the file size to 2^32 == 4 GB). But the FAT+ feature of fat32.ifs allows the 64-bit file size on FAT32 (it is stored in special EA, and bits 32..34 are duplicated in three previously reserved bits of the directory entry. So, first 35 bits are still stored in the directory entry, allowing files with sizes up to 2^35 == 32 GB to store their sizes in the direntry, instead of an EA. If the size is bigger than 32 GB, the full 64-bit size is stored in EAs). But the FAT+ feature is supported with OS/2 only (and with DR-DOS too, but with a bit other way than OS/2. So, you can only move big files on FAT32 disks between different OS/2 copies. WIndows will not understand such big files on FAT32, unfortunately).

I have a 128 GB microSDXC card which I use with mini USB cardreaders. It is used instead of a USB flash disk. I use it for carrying data, as well as for booting from it (most USB microSD cardreaders are bootable). I changed its geometry to normal hard disk geometry and it could be bootable on all my computers. Also, I reformatted it from exFAT to FAT32 as it has more stable support in fat32.ifs and FAT32 is supported by most operating systems. Windows can't be bootable from exFAT, at least. But GRUB4DOS, FreeLDR and QSINIT can boot from both, FAT32 and exFAT. Linux can't boot from exFAT too, at least, with FUSE exFAT driver. Maybe, it will boot with Samsung exFAT driver (if it is compiled into the kernel), but I didn't tried.

306
Hardware / Re: Preparing an USB Flash drive with FAT32 with DFSee
« on: November 13, 2017, 08:27:36 pm »
No need in using any scripts. Usually, the flash disks are partitioned. But some of them are not, like my Silicon Power 16 GB was. In this case, you need to create a partition first. (but if the stick is already partitioned, no need to repartition and reformat)

First, when working with DFSee, you need to select the current disk with File->open object to work with->Partition->...  No need to reformat and repartition. Just add the LVM info, eject and reinsert the disk and it will be seen under OS/2. This is indestructive, you can do this (add LVM info) without losing any files from the stick, as the only info added is the LVM DLAT sector immediately before the partition boot sector. I do this with any friends or clients flash sticks they are carrying to me to pass me their files.

So, usually, you only need to add the LVM info, and it will work fine under OS/2.Those sticks that are big floppies, can be seen with Lars' USBMSD.ADD version. It adds a virtual DLAT sector too, so no need to add it with DFSee. But partitionable media are better and more secure, so, it is recommended to repartition your flash disks. You only create the partition, and that's it.

For booting from flash disks, you may need to normalize the geometry in the partition table. Some BIOSes, like mine, doesn't like some flash disks geometries (cylinders/heads/sectors numbers), and as a result, won't boot from them. So, it is better to redefine the flash geometry to the geometry having 255 heads and 63 sectors per track. This is done with GEO command in DFSee. You can run "geo" without parameters to see the current disk geometry. It will show the cylinders, heads and sectors numbers.

The total number of sectors on the disk is equal to Cylinders * Heads * Sectors. So, you just multiply the current values to get the total number of sectors. Then divide the result to (255 * 63) and you will get the new number of cylinders.

Then wipe the disk with the

Quote
wipe "" 0 2048

command, which overwrites the disk with an empty pattern ("") starting from 0 sector, and rewrite 2048 sectors then, starting from the 0 sector.

Then enter the

Quote
geo Cyls 255 63

where Cyls is the new number of cylinders you just calculated. This should change the current geometry of the disk. Then go to Mode=FDISK->Create new partition, and create a primary partition, occupying all the disk. When operation finishes, quit DFSee, eject and reinsert the disk. Then do lvm /rediscoverprm and the new drive letter will appear. Then do

Quote
format o: /fs:fat32

and format the disk. You should install the latest version of fat32.ifs 0.10 for this command to be working.

But these steps are not mandatory. They can help the flash stick to be capable of booting from it, and to convert the stick from the big floppy to the partitionable one (which will improve the compatibility with majority of OS'es, including OS/2 installations, which haven't Lars' USBMSD.ADD installed) The mandatory thing is a command to add the LVM info. You need to define an explicit drive letter, or set the drive letter to "*:" (which means, the 1st available one). WIthout this, the drive letter won't be assigned to an USB stick/hard disk and the disk contents won't be seen.

307
Hardware / Re: Hardware Reports / Reviews - More - MORE !!!!
« on: November 10, 2017, 05:28:53 pm »
These:

- Logitech Unifying Transceiver
- Logitech Wireless Mouse M280
- Logitech Illuminated wireless keyboard K800

were tested by me on MCP2/ACP2, so I know nothing about ArcaOS. But it should work with ArcaOS too, with big probability. Also, I should note a disadvantage of keyboard k800: It stops responding frequently on pre-boot applications, e.g., pure DOS, BIOS setup, FreeLDR, QSINIT apps. After a cold reboot it works again. And it works fine under OS/2 (I saw no times when it stops responding in OS/2, only in pre-boot environment). It is very annoying, but otherwise, it is very pleasant keyboard (it is wireless, charging from microusb, and having two rechargeable AA batteries inside, which could be replaced to batteries with more capacity. It uses Logitech Unifying receiver, which can be used together with a wireless mouse, like Logitech M280, supporting the same Unifying receiver. I also heard that the you can take two Unifying receivers, plug them into two computers and switch between them via a keypress. I did not tried this, yet, though. I ordered two more Unifying receivers on Aliexpress, waiting for their arrival. Will test them, when they arrive. The wireless keyboards/mice can be paired to an Unifying receiver by a win32 utility, downloaded from Logitech site. It is paired only once, and works without a special software on any OS.) Also, the K800 keyboard has a backlight with adjusted brightness and a sensor of hands proximity. It turns off on inactivity and turns on when you bring your hands to it. Very pleasant in use, except for that it sometimes does not responding (only in BIOS pre-boot environment).

PS: It also has no problem with key autorepeat, as with much newer USB keyboards. I bought another USB keyboard (some OKLICK model, with backlight, too, but it was much cheaper than K800) before this one, and it did not autorepeat keys, when you hold it on. K800, in difference from that OKLICK keyboard, does autorepeat well. I suspect that it is applicable to all Logitech keyboards.

308
Polls / Re: Compatibility with OS/2
« on: November 07, 2017, 02:13:02 am »
2dryeo:

This is not true. This is a common misunderstanding. 16-bit code works in 64-bit mode. Dixie, the author of QSINIT (aka Tetris) said that he safely uses 16-bit IDT/GDT entries together with 64-bit and 32-bit ones. This is EFI version of QSINIT. EFI is 64-bit here, and QSINIT uses some 16-bit routines. So, 16-bit code can coexist with 32-bit and 64-bit ones. Indeed, under "16-bit", many people mean 16-bit real mode code, not 16-bit protected mode code, as 16-bit OS/2 and Win16 are. So, VM86 processor mode won't work in 64-bit "long" mode indeed, but 16-bit protected mode code will work.

309
Applications / Re: Mount ISO as drive letter
« on: November 06, 2017, 09:21:44 pm »
This script: http://ru2.halfos.ru/guru/scripts/files/isomount.zip for NDPISO Netdrive plugin can be associated with .iso files in shells like FC/2, so that, when you tap Enter on an .iso image, it gets mounted. If you tap Enter the second time on the same file, it gets unmounted. You specify a root directory, say s:\iso and mounted .iso's appear as subdirectories under s:\iso. Multiple ISO's can be mounted at the same time. Very easy and convenient.

PS: A bit offtopic, but about mounting images too: For mounting FAT12/FAT16/FAT32/exFAT filesystem images, you can use fat32.ifs 0.10 r328. It includes a f32mount utility, which allows to mount images to a subdirectory on a FAT drive. You run it as "f32mount a:\path\to\file.img w:\tmp" and contents of file.img appear under w:\tmp directory. Also, except "raw" images, I added the code from QEMU emulator, which allows to mount the VM images, like .vmdk of VMWare, .vhd from VirtualPC, .qcow from QEMU, RAW images, etc. You can mount diskette images, as well as harddisk images, a partition number could be specified as "/p:N" too, and an optional offset before a partition table, with "/o:offset". Partition numbers can be primaries from the range 1..4 and logicals, from range 5..255. 5 is the 1st logical partition. Offsets can be decimals, as well as hexadecimals, beginning from "0x". So far, some problems still exist though, and the feature is still alpha-quality, but it is promising :)

310
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?

311
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.

312
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 ;-)

313
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.

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

315
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?

Pages: 1 ... 19 20 [21] 22 23 ... 25