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 ... 8 9 [10] 11 12 ... 24
136
Setup & Installation / Re: VirtualBox Easy OS/2 Setup
« on: November 07, 2018, 09:26:21 pm »
2Rick Hodgin: You should contribute to Netlabs port of VBox, instead of contacting Oracle directly, I think.
Also note that we'll try to put our work in the official Oracle repository in the future.

In fact, ideally the installer should be a simple REXX script. You Unzip the package in some directory, and
run a REXX script. It should modify config.sys, startup.cmd and os2.ini. Also, it's possible to use WarpIN,
but I'd prefer the .ZIP file with a REXX script. unzip+REXX is a better installer for OS/2, in fact. Or, we need
both the WarpIN installer and a .ZIP package with a REXX script, for those who prefer it. I sometimes
need a manual install, so unzip is easier for me.

Though, note that VBox additions require kLIBC and libcx. So, because of this it should be ideally installed
with RPM, to handle dependencies, and avoid conflicts with different versions of the same DLL. Though, on
the other hand, YUM ports could be not installed in the guest. But then, each RPM in the repository is
duplicated by a zipped version of the same package. So, maybe it's better to create an RPM package, and
put it into the usual Netlabs repository. I could help you to create the RPM, if you wish.

So, we could create an RPM installer, plus a REXX script for those who wants to use the zipped versions
of additions.

PS: I plan to package the OS/2 port of VirtualBox as RPM too.

137
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 07, 2018, 02:00:20 am »
2Mauro:

> ok, I sent to you my config,sys lines in a private message, thank you.

Your config.sys looks ok. But I asked for a modified config.sys which causes your system to trap.
So, it's bad that you have it restored to the previous state. Did you BTW commented the

Quote
set greext=panogrex

line? It can cause a trap in PMDD too, because panogrex.dll is a Panorama part,
you should disable it if you use another video driver.

Quote
I keep my mind that saving the machine status in .ova format (if you work in Virtual Box) just before a system update that could prevent to reboot it again, is the more pratical way to obtain the machine as it was before the change.  3 minutes to create the .ova image, 2 minutes for restoring it, if necessary. I know how to go in OS2 recovery menu, I did once, then I do not know how to operate for editing by command line.

Don't you know how to start FileCommander/2 or another VIO-based file manager? Having it in your
system is a must. It's possible to use a command line, only ("cd" and "dir" commands are all you need),
then use "tedit" text editor, which is present in every system (just run "tedit c:\config.sys"), but FC/2 is
easier. You just add it to PATH and all you need to do, once in the command line, is to start "fc".

Too bad that you cannot use simple shell commands. I thought, every OS/2 user knows them. It's
the basic skills every user should know. If you don't know it, I could not help you :(

138
Utilities / Re: XDF disk extractor
« on: November 07, 2018, 01:29:33 am »
2Gregg Young: Is not wl.exe just a renamed wlink.exe? The only difference, it seems, is that wl.exe is built statically. wlink.exe is linked to wlinkd.dll. And wrc.exe from Watcom is linked with wrcd.dll. Wrc.exe from yum repository is built statically too. I just took wlink.exe from OW 2.0 (Frank's build) and renamed it to wl.exe, and relpaced the previous version of wl.exe with it. So yes, I built VBox successfully with these versions of wlink.exe and wrc.exe from Frank's site. The only parts built with OW 1.9 are BIOS and Video BIOS ROMs. They fail to link with wl.exe from OW 2.0. The error from linker is:

Quote
Error! E2011: file L:\src\vbox\prev\out\os2.x86\release\obj\VBoxPcBios32\VBoxPcBios32.lib(L:\src\vbox\prev\src\VBox\Devices\PC\BIOS\pci32.c): invalid object file attribute

139
Utilities / Re: XDF disk extractor
« on: November 06, 2018, 03:49:21 pm »
2Gregg Young: Oh, nice. So, you added the "WINDOW" keyword to wrc.exe? (Or it's Steven's fixes?)
IIRC, the version from OW 1.9 didn't supported adding resources to OS/2 binaries during the linking,
though, it did support that for windows binaries. But supported adding resources to existing OS/2
binaries (after they are linked). So, it's good to know if newer versions of wrc from OW 2.0 support
adding resources to OS/2 binaries during linking?

140
Utilities / Re: XDF disk extractor
« on: November 06, 2018, 03:38:51 pm »
2Rick: Yes, it's 11 sectors per FAT. Not sure, where 9 sectors were used. 1 reserved sectors + two
11-sector FATs. 1+2*11 = 23 sectors == 1 usual track. Though, DOS/BIOS only sees the
hidden image which is 19 sectors long. Hm.

I didn't read the article to the end, yet, though

PS: Yes, 1.44 MB DS/HD indeed uses two 9-sector FATs. XDF format uses 11 sectors per FAT,
so here Michal is right.

141
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 06, 2018, 02:54:38 pm »
2mauro: Why do you need to backup the VM as .ova? It can be fixed without that -- using the
same techniques you use with OS/2 on real hardware. So, all you need is return your config.sys
as it was before your modifications. You remember what did you modified, don't you? You can
always boot OS/2 to the "recovery choices" menu and go to the command line, and edit your
config.sys. (As always, press Alt-F1 when the white brick with the "OS/2" caption on right appears.
So, the "recovery choices" menu should appear. Then choose "F2" to boot in the command line.
Didn't you used it before? Once you're booted into the command line, you can start tedit, FC/2,
or any other text editor you like). And you return your video driver back to GENGRADD or VGA
from the "recovery choices" menu, in case of any video driver troubles. So, you could return
to a GENGRADD driver, then replace it to VBXGRADD, as I described before.

PS: You can post your config.sys, i could look at it. Startup.cmd doesn't matter, most probably.
I doubt it can make any troubles. All you need from it is start VBoxService here. It looks like you
have video driver troubles. So, revert to GENGRADD and try installing the additions again.

142
Utilities / Re: XDF disk extractor
« on: November 06, 2018, 11:00:21 am »
2Dave Yeo: Thanks for the link. MichalN blog is a good reading, indeed.

2Rick Hodgin: The root directory end at offset 0x4a00 (sector 37 (if sectors are counted from 0)). But
I see the "hidden root directory" repeating again here (a "WIN1" volume label and a "packing.lst" file again).
Why it's again here? We need to read the article in MichalN blog, and see, I think.

143
Applications / Re: Shared folders IFS for VBox Additions, the test version
« on: November 06, 2018, 09:57:37 am »
2mauro: No fully automated procedure. I'd avoid automated config.sys modifications.
It should be modified by hand, because it's easy enough. Uninstalling drivers in case of
problems is easy too. You can boot to command line and fix your config.sys. It is not
windows, everything is user-controlled. So, please set up your video driver correctly,
until you install vbxgradd.dll.

144
Setup & Installation / Re: LIBVPX?.DLL
« on: November 05, 2018, 05:04:07 pm »
2Andre Helldoorn: and VBox used to use it even earlier than Mozilla. VBox uses
it to record screencasts. (which can be viewed with Mozilla, for example)

Though, VBox is not yet packaged as rpm.

145
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 07:21:35 am »
2Dave Yeo: Good to know. So, it is an official build indeed.

2Rick Hodgin:

Looking at the diskette I uploaded, ftp://osfree.org/upload/win1.dsk, I tried to check
it with CHKDSK and got:

Quote
[l:\data\vm\bochs]chkdsk j:
The current hard disk drive is: J:
The type of file system for the disk is FAT32.
The FAT32 file system program has been started.
FAT32: Unicode translate table for CP 866 loaded.
Error: Next cluster for 2 = 00000FF7
Error: Next cluster for 3 = 00000FF7
Error: Next cluster for 4 = 00000FF7
Error: Next cluster for 5 = 00000FF7
Error: Next cluster for 6 = 00000FF7
FAT32 version 0.10.r378 compiled on Oct 16 2018
The volume label is WIN 1.
The Volume Serial Number is E300-0000.
The type of file system for the disk is FAT12.

CHKDSK is checking fats :  0%
SYS1374: File Allocation Table (FAT) is bad on drive J:.
The copies of the FATs do not match
Please run CHKDSK under Windows to correct this problem


Errors found.  The /F parameter was not specified.  Corrections will
not be written to disk.

Looking at it in the hex viewer, I can see that the 2nd FAT copy is truncated.
It begins at 0x1800. Sectors #1 and #2 of the 2nd FAT begins with:

Quote
00001A00:  F9 FF FF 03-40 00 FF 2F-00 00 00 00-00 00 00 00  ∙  @  /

What is this? Sector #3 starts with

Quote
00001E00:  57 49 4E 20-31 20 20 20-20 20 20 08-00 00 00 00  WIN 1      
00001E10:  00 00 00 00-00 00 00 00-00 00 02 00-00 00 00 00            
00001E20:  50 41 43 4B-49 4E 47 20-4C 53 54 01-00 00 00 00  PACKING LST
00001E30:  00 00 00 00-00 00 00 00-00 00 02 00-00 08 00 00              

This looks like a directory containing a volume label "WIN1", followed by a file
directory entry for "packing.lst". Sectors #4-#7 contain the contents of that file.
And sectors #8-#10 contain zeroes. Then, staring at offset 0x2e00, starts a root
directory. It also starts from a volume label "WIN1". Note that the volume label
should be in the root directory, only. So, I wonder why sector #3 contains another
root directory. And the real root directory doesn't have the "packing.lst" file. So,
what is that packing.lst file and the second root root directory for? It appears that
second FAT is used to store some special data: a separate private root directory
with a file which lists the files contained in the real root directory! And these file and
directory are preceded with some more unknown data.

Also, this diskette has 484352 bytes of free space, according to fat32.ifs.
According to your utility, it has 485888 of free space. The difference is 1536 bytes,
which is 3 sectors/clusters. Can you check what PCDOS shows on this diskette?

And diunpack, like CHKDSK, sees that two FAT copies are not the same, this is
why it fails to extract files.


146
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 05:07:57 am »
2Rick:

> The updated file's been posted.  Valery, please try this one to see if it works for you.

Now setup.inf extracted ok for me. Also, comparing file contents with the same files
in the image mounted with fat32.ifs, shows that the files are identical.

So, it now seems to work ok.

147
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 04:49:37 am »
FAT entries correspond to clusters, not sectors. Though, a cluster on a floppy is usualy one sector. But
floppies with bigger clusters are possible too. FAT entries 0 and 1 are reserved. Entry 0 starts with the same
byte as the media byte in BPB. The media byte is usually 0xf8 on fixed disks, and 0xf0 on 1.44 MB floppies.
360 KB, 1.2 MB floppies have special values for that byte. In fact, the very old FAT disks had no BPB, they
identified media formats with a media byte in the 1st byte of FAT. Later, BPB was introduced as a more
universal mechanism of defining the disk formats. But the 0 FAT entry remained the same for compatibility.
Entry 1 is also reserved. Since Win95, it is used for storing the "dirty" bit of the FAT volume (it is ignored
on floppies, but used on hard disks). Entries starting from 2 describe clusters of data area. The data area
on FAT12/FAT16 start after the root directory. The root directory fas fixed size, specified in the BPB, it cannot
grow. So, the first are reserved sectors. Then follow the FAT copies. The FATs are followed by the root directory.
After the root directory ends, the 1st cluster begins. So, FAT entry #2 correspond to 0 cluster, FAT entry #3 --
to 1 cluster, and so on. So, you should subtract 2 from the FAT entry number, and you'll get 1:1 correspondence
(FAT entry no. - 2) -> cluster number. So, clusters 0 and 1 not correspond to any sectors on disk, they should
be skipped.

On FAT32 and exFAT, the root directory must not immediately follow FATs, and its size is not fixed, it can grow.
Also, in difference from FAT12/FAT16, the root directory on FAT32/exFAT can be fragmented. Also, root directory
area is not reserved on FAT32/exFAT. It is located in data area, and has cluster number assigned. On FAT32, if
the root directory starts after the last FAT immediately, it occupies cluster #2 (and corresponds to FAT entry #2).

148
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 04:16:18 am »
2Rick:

Quote
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

This seems to be because, as you said, on track 0, only first 19 sectors are used. The
last 4 sectors are skipped. So, this place seems to be the hole in FAT table, this is why
diunpack says that FAT is corrupt.

I think, the hole should be handled specially. So, I wonder, how FAT32.IFS works
without the proper handling of that hole.

2Dave Yeo: Another fork at https://efbe.musca.uberspace.de/ seems to be better,
they seem to have OS/2 code not broken I tested it today. The beta3 on Netlabs' ftp
is that Steven Levine is working on. But it seems to be the same as Github fork, and
we get linker errors on some VBox code. The wl.exe and wrc.exe from yum repo seems
to be from Steven too.

149
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 03:29:45 am »
2Rick:

Quote
[setup]
    help = setup.hlp

;   Place any programs here that should be run at the end of setup.
;   These apps will be run in order of their appearance here.
[run]

...

You can try searching these strings in the image with a hex viewer.

150
Utilities / Re: XDF disk extractor
« on: November 05, 2018, 03:15:17 am »
Yes, the file size is 1884160 (you can download it and see). The reserved sectors are == 1.
It seems to be the same for all diskettes.

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