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 ... 9 10 [11] 12 13 ... 24
151
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 03:07:19 am »
Rick, I tried to extract this file: ftp://osfree.org/upload/win1.dsk with your
program and see that the setup.inf file corrupted. If I extract it with my
method, the same file contents are ok, it's a simple text file. But most
files seem to be extracted fine.

152
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 02:44:25 am »
Yes, the same in OS/2. The boot disks 0-2 are standard 1.44 images, and disks 3-...N are
1884160 bytes == 1.796875 MB XDF images. diunpack won't extract them.

153
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 02:29:04 am »
Quote
L:\data\vm>vfctrl ?
VFDisk Control Program
  The possible commands are:
    Query VFDisks:  d:\os2\vfctrl.exe
    Help         :  d:\os2\vfctrl.exe ?
    Query VFDisk :  d:\os2\vfctrl.exe X:
    Set VFDisk   :  d:\os2\vfctrl.exe X: <nn>
       where <nn> is one of the following:
         0 EJECT
         1 1440 1440K 1440KB 1.44 1.44M 1.44MB
         2 1200 1200K 1200KB 1.2 1.2M 1.2MB
         3 720 720K 720KB
         4 2880 2880K 2880KB 2.88 2.88M 2.88MB
         5 360 360K 360KB
         6 1840 1840K 1840KB 1.84 1.84M 1.84MB

L:\data\vm>vfctrl x: 6

L:\data\vm>loaddskf WIN1.DSK x:

Unsupported disk type

So, vfdisk doesn't support XDF disks too, and disks of "6" format having
1840 bytes per sector, differ from XDF ones. But I think, it's possible to add
support of 23 sectors * 80 tracks * 2 sides disks to vfdisk, and it should
work.

154
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 02:17:51 am »
Interesting.

> The XDF format "tricks" the FDC by indicating on the track record that it has 39 128-byte sectors.  But, the FDC does not rely upon that track record setting for each of the sectors within, and instead the OS sends sector size information for each sector.  So, it uses four separate sizes for the space around the track, resulting in one 512-byte sector, one 1024-byte sector, one 2048-byte sector, and one 8192-byte sector.

So, this is only a trick for programming the FDC (at physical level).

> But, logically, the entire image inside the XDF is arranged as 23 sectors of 512 bytes.  Track 0 only uses 19 sectors, however, so the last 4 are simply ignored.

So, on logical level, XDF image is just an usual sequence of 23*80*2 sectors 512 bytes each == 1884160 bytes. So,
the problem of windows image programs is that it has 23 sectors, not 18?

Hm, but why then diunpack doesn't work with these images? It should.

Quote
L:\data\vm>diunpack WIN1.DSK -d aaa\


DIUNPACK.EXE Release 3.00 12-20-95
Copyright (C) IBM Corporation 1995
All rights reserved.


Reading disk image....


ERROR: Image file fat is corrupt
[/quite]

155
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 02:01:36 am »
Regarding the OpenWatcom 2.0: I just tried a daily snapshot of OW 2.0 from here:

https://efbe.musca.uberspace.de/

I just compiled fat32.ifs with it successfully. Previously, I tried another OW 2.0 from
GitHub, and had problems with it. The FS utility DLL won't build. It contains a 32-bit
source which implements CHKDSK/FORMAT/SYS/RECOVER routines. These routines
are 16-bits. So, the 16->32-bit wrappers created with 32-bit C compiler, doesn't
compile. The 32-bit compiler is broken. But the build from the former site is working
fine. The only bad thing I noticed is that it seems to compile significantly slower
than OW 1.9.

156
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 01:53:09 am »
2Rick Hodgin:

> I appreciate your help, Valery.  It's been nice to have that little extra insurance to nudge me along. :-)

Thanks! :)

157
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 01:51:32 am »
2Rick Hodgin: Indeed, I tried two 1.8 MB diskette images from Merlin, I mounted them
successfully with fat32.ifs+loop.add. I was able to copy the diskette contents out of
the image! So, it is working, though, copying is slow, for some reason. Maybe, this is
because of sector interleave?

Also, as far as i understand, these XDF diskettes have 128 bytes per sector? So, it's
working with such sectors! (I also successfully tested 2048-byte sectors. FAT32 can
mount CD's with FAT/FAT32/exFAT file system. And its FORMAT/CHKDSK/SYS utilities
also work with CDRW/DVD+-RW/BD-RE disks in packet mode. So, it is tested by me
too and is working).

But strange why then windows utilities have problems with XDF images? Is it only
because sector size is hardcoded in most of them to 512 bytes?

158
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 01:32:32 am »
PS: I have some XDF images, but only those available on OS/2 installation disks (Merlin, Warp3).
These are the same you have, so they doesn't contain subdirectories.

159
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 01:15:06 am »
2Rick Hodgin: Nice, so you got the free space calculation to work without my help?

Quote
And, if I could get Arca Noae's support/help, I would be happy to write an xdfmount utility which would mount an XDF image as a RAM disk, allowing it to be changed/updated as needed, and then when it's unmounted it would write the changed contents back to the XDF disk image so it can be re-written to a real floppy disk if need be.  Also, an option to save it to another XDF filename.

I think, there is a better option than to mount an XDF file as a ramdisk. In fact, I already added
the support for different disk images to fat32.ifs. FAT32.IFS now is able to mount the FAT/FAT32/exFAT
disk images at the subdirectory on another FAT/FAT32/exFAT file system, serving as a mount point. Also, with my
loop.add block device driver, I can mount any filesystem, contained in a file, to a drive letter. This include
not only FAT/FAT32/exFAT filesystems, but any other FS having an IFS driver for OS/2. Except for
FAT/FAT32/exFAT, it can mount the CD ISO images, floppy images, any "raw" disk images and different
VM images, like .vhd's from VirtualPC, .vdi's from VirtualBox, VMWare's .vmdk images, etc (see details
in fat32.inf file from FAT32.IFS). For supporting VM disk images, I ported a library from QEMU, qemuimg.dll.
This DLL is loaded by cachef32.exe daemon, and the daemon executes read/write operations by request of
the IFS or of loop.add driver. Currently, it works fine for mounting FAT/FAT32/exFAT/CDFS file systems. JFS
and HPFS inside disk images are mounted successfully too, with the help of loop.add, but there are currently
problems with I/O request via strat2/strat3 routines: when you start copying files from/to the HPFS or JFS
image, it starts copying, but when cache is flushed, it hangs. Not resolved it yet. But for FAT/FAT32/exFAT/CDFS,
which don't use start2 and caching, everything is working fine, without hangs.

So far, the qemuimg.dll lib supports the following disk image formats:

1) RAW disk images, including diskette and CD ISO images
2) Bochs VM images
3) Linux CLOOP (Cryptoloop) images, used by Knoppix LiveCD
4) Macintosh .dmg
5) VirtualPC .vhd
6) VMWare .vmdk
7) Parallels
8) QEMU vvfat, qcow, qcow2 formats
9) VirtualBox .vdi

Also, I planned to try adding support for compressed .dsk floppy images from IBM.
So, I'd suggest you to add the XDF support to this lib too. So, qemuimg.dll lib could
be reused by many different programs in theory, not only fat32.ifs/loop.add.

160
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 04, 2018, 03:54:20 pm »
2Martin: Are you sure you started VBoxService.exe successfully? You should add it to
startup.cmd, otherwise Additions will not work. VBoxService.exe automounts all shared
folders, so you don't need to mount them manually. Also, it handles the shared clipboard
too. If shared clipboard is not working, then most probably, VboxService.exe is not
running.

> The command mounts the W: drive, but it shows empty in the GUI (known issue #1, right?). On the command line it list something but without file names (Check picture)
>I'm not sure if there is another requirement that I'm missing. Anyways, it looks very promising.

As I said, WPS Drives object is not working at the moment. CMD.EXE doesn't work too, indeed
(because not all DosFindFirst flags are working yet). But File Commander/2 and 4OS/2 work fine.
Also, command.com and Volkov Commander show file listings in a VDM (though, the file name
translation short <-> long is to be implemented, yet -- similar way as it's done in fat32.ifs for
exFAT).

PS: Hm, indeed, looks like shared clipboard is not working, even with VBoxService.exe running.

PPS: It appears that VBoxService.exe quits after it mounts the shared folders. Need to see why.
This is the reason why shared clipbord is not working -- it requires a running VBoxService.

161
Utilities / Re: XDF disk extractor
« on: November 04, 2018, 03:40:02 pm »
2RickHodgin: FAT32 has a special field in FSInfo sector (the next sector after the boot sector), which
contains the count of free clusters. exFAT has similar field, IIRC, too. But FAT12/FAT16
has no such field and it calculates free space each time it mounts/accesses the medium.

The free clusters are just counted, from the FAT table. You just run a loop through all FAT
entries, from 2, to TotalClusters + 2. FAT entries 0 and 1 are reserved, so the 1st data cluster
is 2.

TotalClusters = (TotalSectors - StartOfData) / SectorsPerCluster;

TotalSectors and SectorsPerCluster are the fields from BPB.

StartOfData = ReservedSectors + SectorsPerFAT *
NumberOfFats + (RootDirEntries * sizeof(DIRENTRY)) / BytesPerSector +
((RootDirEntries * sizeof(DIRENTRY)) % BytesPerSector) ? 1 : 0;

Where sizeof(DIRENTRY) == 32. -- This is as I see the code from fat32.ifs (FAT case).
All the above variables are BPB fields. So, when you calculated the number of free
clusters, you should multiply it by SectorsPerCluster, and divide by BytesPerSector,
so you get the free space in bytes.

162
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 04, 2018, 01:55:33 pm »
2mauro: There are the instructions in the official readme on Oracle's Additions ISO,
though, it is brief too. Mine is even more thorough :) Not sure, what's not clear for
you? You should copy all the files in respective directories (or somewhere to \programs,
or whatever directory you use for installing apps). Only vbxgradd.dll should be on the
LIBPATH. Any other programs can have arbitrary location. You should have any GRADD
driver installed, prior to vbxgradd.dll installation (GENGRADD, Panorama or SNAP are
good).

You need to use VBoxMouse.sys instead of mouse.sys (just comment it out). So all you
need is the following statements in config.sys:

Quote
device=\...\VBoxGuest.sys
device=\...\VBoxMouse.sys
ifs=\...\VBoxSF.ifs

set c1=vbxgradd

You should comment out mouse.sys and the "set" line for your previous GRADD
driver. If something is not clear, please tell more specifically :)

PS: And yes (I forgot to mention), you need the latest kLIBC and libcx installed
into your guest, because the Additions are built with GCC.

> Tried to install the official ones I had an unrecoverable trap stop on rebooting
similar to what shown by Martin here above, and would be nice having more
luck with these.

The trap in PMDD usually means that you have your video driver misconfigured.
So, you only need to install it correctly.

163
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 04, 2018, 01:37:45 pm »
2Martin: You don't need Panorama, as VBox uses it's own video driver. Though,
you can install Panorama (or SNAP) first, and replace its GRADD driver with that
from VBox. VBox video driver can be installed over any existing GRADD driver,
including GENGRADD.

So, you had that trap in PMDD if you install vbxgradd.dll without prior install
of Panorama?

Quote
How is supposed to mount the drive on the OS/2 guest? Something like
"net use x: \\vboxsvr\share" ? Which protocol is it needed for this, NETBIOS ?

Shared folders are attached like this:

Quote
VBoxSFAttach w: 1.-os2

in your case. Though, it is usually not required. All shared folders you specified
in the VM config will be mounted automatically.

NETBIOS has nothing common with shared folders. You don't need to install
any network protocols for them. Shared folders is the VM feature. The VM
exposes some host machine disks to the guest. To access them, the shared
folders IFS calls API's in VBox. So, the guest just communicates with the host
side. There are special services run on both, the guest side, and the host side.

PS: I tested it successfully with VBox 5.2.20 on Linux host. The additions are
built with 5.0.51.

164
Utilities / Re: XDF disk extractor
« on: November 04, 2018, 02:34:13 am »
2Bogdan: So, xdfloppy.flt is required to support XDF on OEM ABIOS machines with the
same ibm1flpy.add driver as with non-ABIOS machines? I.e., xdfloppy.flt handles the
differences between these two types of machines, so that, ibm1flpy.add is independent
from that? Or I misunderstand?

165
Networking / Re: OS/2 4.52 to VirtualBox networking
« on: November 04, 2018, 12:08:24 am »
Just tried the port forwarding in OS/2 host. On a WinXP guest, I enabled
the telnet service. It has the address:port 10.0.2.15:23. My OS/2 host
has IP 172.30.0.218. So, I enabled the TCP port forwarding from
172.30.0.218:223 on host to 10.0.2.15:23 on guest. So

Quote
telnet -p 223 172.30.0.218

works. I was able to login into the WinXP telnet service, everything
is working fine!

Pages: 1 ... 9 10 [11] 12 13 ... 24