• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu
Menu

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.

Show posts Menu

Messages - Radek

#31
My guess is "not odd video but the ancient chaos". In those old days, every video card had its extras, its special video modes, and its special way of enabling them. These extras were supported by native video drivers but they usually aren't supported by SNAP or Panorama. SNAP usually restricts your fullscreen to (available) VESA modes. Panorama does not seem to support more than standard BIOS video modes (00h - 13h) in DOS sessions. In OS/2 sessions, it need not be better.

Check which VESA modes are supported by your comp. There exist a 132x50 VESA modes, which might be usable when rewritting "something weird". Note that not all VESA modes, which should be available on your HW, can be reported as available. The reason is the current very bad coding of VESA BIOS: Winblows does not need VESA so that BIOS coders do not waste time with implementing it and if they show any effort in implementing then the result is incomplete and full of bugs. I have seen "VESA VBE 2.0 compatible" video card which supported only 640x350x16 and 640x400x16 VESA video modes. Period.
#32
As far as the image is concerned, Linux PING (partimage isn't ghost) can do that. It's a bootable ISO, which can backup a partition storing only used sectors and bzip-ing them - so that the resulting image will be even smaller than 740 MB. PING knows HPFS. It knows JFS but I have no experience with backuping JFS partitions. Next, you can unpack the image to the SD card.

I have installed eCS this way on my comp with USB CD drive until eCS was able to install from an USB CD (RC6a): take another comp, install eCS there, PING the partition, put it on your (my) comp, adjust, boot - if okay then redo the image and store it as your "installation CD".

You will need to adjust HW and partition parameters after unpacking - everything has been backuped and reset by PING.
#33
http://www.os2world.com/component/option,com_smf/Itemid,63/topic,2042.0/

Ubuntu 9.04 was able to use the "good" GRUB 0.97 (on ext3) or the "cursed" GRUB 2 (on ext4). Perhaps, you are using the "good" one :) Real problems seem to start with 9.10
#34
AFAIK, the problem is with GRUB 2, which is incompatible with BM and eCS. Ubuntu 9 and later versions use GRUB 2. A "normal" GRUB (version 0.9, used by Debian, for example) is okay.

If there is a method of installing Ubuntu 10, then the main step will be bypassing GRUB 2. I have heard that it is possible to install Ubuntu 8 (which contains GRUB 0.9) and then upgrade. Install GRUB on the Ubuntu partition and do not make the partition startable. Then install eCS and enable Ubuntu from the LVM. Your boot manager is BM, you will "boot" GRUB from it, which will boot Ubuntu in turn. I am running Debian and eCS on my comp this way. Earlier, I had Ubuntu 8 and eCS.

My own experience: Ubuntu (and Debian) should be installed on a primary partition. Logical partitions are incompatible in Linux and eCS somehow. If you install on a logical partition, you can get errors in LVM and no possibility to make the partition bootable or added to BM menu but you can still enable the partition using DFSee and it will work. Well, it's not good to have bad partition structure on a disk.

Beause more and more Linux systems can be expected to use GRUB 2 in the future, the eCS gurus should do something with it. Linux cannot be expected to take any action.
#35
First of all, I am joining Ivan: which version of OS/2 are you using? Warp 3 (up to late fixpacks) and Warp 4 (up to FP6) cannot install to a 7 GB disk without patching installation diskettes. You will need to patch installation diskettes with Daniela's HD drivers (files dani*.zip on hobbes.nmsu.edu). The dani* drivers allow you to use 7 GB disk even in Warp 3, but you will need some older version of the driver (for example 1.7.0) with W3. W4 will run with all versions of the driver except the latest ones (1.8.5 and later). eCS comes with Daniela drivers and it will install on a 7 GB disk.

Next, which disk layout you want to achieve? Are you installing Boot Manager? Are you planning to create more partitions on the HD?

If you are installing installing Boot Manager then you need to install BM, create a partition, make the partition bootable and add the partition to the Boot Manager menu. Otherwise, the Boot Manager will not find the partition after reboot. If you are not installing BM then create a partition and make it bootable. This should be enough.

I recommend creating only one partition (the one where you are installing) and doing the rest after completing installation. You will have more comfort from the running OS/2 than from the installer.
#36
It's a problem of domains and user names. IIRC, you need to set the eCS this way:

workgroup = your domain name
user = your name in your winblows

Then you should be able to connect to the web from your virtual machine. It worked with my eCS running on winblows XP on our institute web. I am using Innotek VPC but it should work in the VPC fouled by Big Bill, too.
#37
I am not authorized to view this resource. Therefore, no comments  ;D
#38
Storage / Re: ext2 driver in eCS
2010.12.01, 17:33:04
FAT32 partition seems to be the only possibility. AFAIK, there is no Linux HPFS driver. eCS version of JFS is not enough compatible with Linux, and the archaic ext2 driver you have found is the only ext2 driver available in OS/2 and eCS. Moreover, ext2 is rather archaic, too, the current "ext" is ext3 and ext4, so that you could experience problems with an ext2 driver.

I am running a "multiboot" Debian - eCS machine and I use a 5 GB FAT32 partition for passing files between Debian and eCS. I haven't seen any problems.
#39
(1) Rename Daniela's drivers to the "standard" names. dani1s506.sys to ibm1s506.sys, daniatapi.flt to ibmatapi.flt .
(2) Replace ibm1s506.sys and ibmatapi.sys on the diskette with your drivers.
(3) Make sure that the config.sys on the first diskette contains SET COPYFROMFLOPPY=1 . Add this statement to the config.sys if it isn't there.

That's all. Notes:
(1) Most likely, there won't be enough space on the first diskette. You can delete tedit.exe along with related files from it. tedit is on the second diskette again so that you aren't losing it. You can also delete SCSI drivers (if your machine isn't SCSI) from the diskette.
(2) If you have dani1s506.sys ver 185 or later then (a) you need daniatapi.flt ver. 040 and (b) you are risking because ver. 185 and later is for eCS and need not work with W4. If you have dani1s506.sys ver. below 185 then you need daniatapi.flt ver. below 040. dani1s506 ver. 170 with daniatapi ver. 037 work with W4.
(3) You can patch the corresponding BASEDEV statements in your config sys instead of renaming the drivers. The file names of the drivers aren't "mandatory".
#40
I think reinstalling is the best option. If you decide to reinstall, then:

- boot from eCS CD (or OS/2 diskette) and create a partition for your winblows. Create it "from the beginning of the HD". Do not create any other partitions. Save changes, quit FDISK, reboot.
- boot from winblows CD and install winblows on this partition.
- boot from eCS CD, install boot manager, create other partitions, install eCS.
- start eCS, run LVM (the PM "mini LVM" app is okay) and add the winblows partition to the boot manager menu.
- reboot. Now, you will have both eCS and winblows in the BM menu and both systems should run.

I have installed both eCS and winblows 2000 on my comp this way.

Warning! NEVER allow winblows "hard disc manager" to run. This can clobber your partitions and prevent eCS from running. Do all HD maintenance from eCS.
Note: When you install winblows (at leas some versions of it), the installer tends to foul all partitions it finds. That's why you start with a single partition on your HD - nothing to foul, sorry. If you create other partitions or install eCS first then you can experience problems.
#41
Article Discussions / Re: Ports
2010.10.09, 22:05:18
DosBox is awfully slow. Moreover, DosBox has big problems with colors in eCS and also with non-US keyboards (both in eCS and Debian). On the other hand, eCS has a perfect support for VM86, where the old DOS games run like hell - but without sound and with problems with installation on contemporary HDs. I would like to see a project branched from DosBox which would contain:

(1) A virtual sound driver which would pretend a Sound Blaster to a DOS session and which would pass the sound data to Uniaudio. Most of us use Uniaudio so that supporting only Uniaudio shlould not be too restrictive. A basic implementation of an older version of SB should be enough. DosBox can already do that.

(2) A virtual CD driver which would mount an ISO image and pretend a CD in a DOS session. There exist isofs.ifs by P. Ratcliffe but isofs.ifs mounts an ISO as a network drive - unusable for games which insist on their CDs. DosBox can already do that.

(3) A virtual hard disc which would pretend a HD of a suitable size for the old DOS apps. In fact, a "subst" command improved by an ability to lie about free space. DosBox can already do that.

(4) An UMB manager (a QEMM loadhi command) which would be able to put a TSR into UMB without need of linking from "conventional memory". Reserved areas at the end of conventional memory are problem sometimes. Example: TES Arena and PS/2 mouse. You get "not enough memory" error no matter how much memory you free. According to Betsehda, this is a bug in PS/2 mouse but it is a blunder or Arena because moving ABIOS high using QEMM solves the "bug" immediately. DosBox does not help here.
#42
Hardware / Re: My Cell Phone and eCS 2.0
2010.09.07, 13:03:23
(1) As far as CONFIG.SYS is concerned, run usbcfg7a from Hobbes. It will show you your current settings and the settings needed for your comp. It can also fix the wrong number of drivers in your CONFIG.SYS . This is the simplest way of putting the right number of USB drivers in your CONFIG.SYS .

(2) Even if the phone card behaves like an USB mass storage, you need not be able to read/write it from eCS. I have a similar problem with my Nokia E51. I can connect the phone to my comp using an USB port. I get a message that the card "is now not in the phone" that means, the card is operated by something else (by the comp). But I cannot read the card from my eCS. I can read it both from winblows and from Debian.
#43
I have found version 1.7.0 of the driver in my archives. The driver should work with W4. I can email it to you if you post me a PM with your email address.
#44
The possible source of problems can be the version of Daniela's drivers. The latest versions are for eCS. Try some older versions: 1.6.x for example, you find them on Hobbes. These versions should work with W4. You will need to replace ibm1s506.sys and os2dasd.dmd with Daniela's drivers at least.
#45
The disk size does not seem to be the problem. The IBM driver was able to handle disks up to 8 GB (LBA mode). Daniela's drivers could help if the disk weren't "standard". But then - why was the comp shipped with OS/2 drivers? Or, does the OS2 directory contain also other drivers, for example, a HD driver?

The instructions posted by cblackm are pretty clear, they should be OK. What's wrong is a mystery, especially because the instructions came from the vendor. I suggest the following:

(1) Check the BIOS settings (if it is possible). The HD should be in LBA mode, the CHS data should correspond to the 6 GB size.
(2) Comment out the os2cam.add driver and try to install. You should get a message that your CD cannot be operated by the installer. If you do then the HD isn't guilty most possibly.