OS2World OLD-STATIC-BACKUP Forum

Public Discussions => General Discussion => Topic started by: Saijin_Naib on 2007.12.27, 07:41:33

Title: eCS 2.04 RC4
Post by: Saijin_Naib on 2007.12.27, 07:41:33
Hey, just released not too long ago! I am downloading now, testing in VPC later tonight (?) or tomorrow. 11%, 74kbps.

Updated eComStation Wiki page to reflect this newest release.
Some infos:
==== WHATSNEW for eComStation 2.0 RC4 ====

-=# The Christmas 2007 release #=-

New Features:

* Network reconfiguration now functions properly
* Detection of wired vs wireless NICs will be in proper order
* Added tool to configure a not-connected wired NIC interface (llaecs)
* Disk resizer has progress bar for improved usability
* New bootlogo and desktopbackground, reflecting "RC4" status

Updated Applications:

* Updated GenMac to "Release Version 2.20 RC1"
* Updated XWLAN utility to version 3.10 RC1
* Updated ACPI to version 3.05
* Updated both Firefox and Thunderbird to version 2.0.0.11
* Updated RSJ CD writer to 6.02
* Updated UniAud audiodriver to 1.1.4RC4 release
* Updated UnixLike utilities to support wildcard notation
* Updated tar (to 1.18), gzip (to 1.3.6) and bzip2 (to 1.0.4)
* Updated DOS kernel to 14.103
* Updated Time zone update for Java 1.4.2 to 2007H
* Updated MPTS Wrap to version 0908

Fixes since the previous release:

* 1686: [installer phase 2] Problem with OBJECT ID of mouse object
* 1796: [installer phase 2] GenMac needs to be installed completely on HD
* 1190: [other] APM Installation: config.sys missing: SET ENH_SUSPEND=2
* 1626: [booting of CD] XUL disc resizer
* 1633: [installer phase 1] Broadcom NeteXtreme Gigabit NIC not detected
* 1704: [other] If both GenMAC wirless interface and second inteface have
        TCPBuei enabled, Peer will not start
* 1625: [installer phase 2] eCS 2.0 rc2 error code 85 when USB CD-ROM
        support is requested
* 1800: [other] Apply ABIOS patch to OS2LDR
* 1700: [installer phase 3] ecs 2.0 it_it rc3: finalization wizard writes
        USER variable uppercase
* 1583: [other] Included versions of archiving utilities like tar, gzip,
        bzip2 are not the latest versions
* 1572: [installer phase 1] SEINST install failed
* 1711: [installer phase 1] System crashes without /!BIOS
* 1752: [installer phase 1] Trap E in OS2KRNL on starting install
* 1672: [other] Shutdown menu (estyler) does nothing if no selection is made
* 1707: [other] selecting panorama causes finish.cmd to run makewps.cmd
        from snap
* 1685: [other] Network reconf no longer works
* 1795: [other] Selective installer for networking destroys system
* 1738: [other] After successful installation, 'Selective Install for
        Networking' causes a loop in phase 2
* 1607: [installer phase 1] Broadcom 10/100 network adapter not present in
        macs listing.
* 1198: [other] Do not run CFGSORT on (network) reconfiguration
* 1732: [other] NIC not detected on HP compaq NC6320
* 1659: [booting of CD] Experimential features
* 1564: [other] (eCS 2.0 RC1) WPSEXTS missing
* 1781: [other] wpsh.ir is down level.
* 1669: [other] Amouse needs /SMP switch in SMP mode
* 1712: [installer phase 2] LAN not working, IBMLVL.INI not readable by
        MPTS.exe
* 1789: [other] JUNE.LNG misses texts and one sentence needs modification.
* 1504: [other] On this system V2.0B4 using GenMac for Broadcom NetXtreme
        NIC failed to install ANY copy of mptn.msg
* 1631: [other] mptn.msg missing
* 1580: [other] changing video drivers results in an unstartable system
* 1720: [other] Missing menuitems: Create another.., Create program object
* 1746: [other] Need to update the Samba client code in the EVFS package
* 1777: [installer phase 1] LVM fingerprint check text needs fixing
* 1722: [installer phase 2] Trap 000e ThinkPad R61
* 1724: [installer phase 1] Due to HW detection order Wireless is put on lan0
* 1641: [installer phase 1] Dual Core CPU installs W4 Kernel with "/SMP"
        option in ACPI.PSD. Result: stop at bootlogo.
* 1750: [other] FAT 32 IFS
* 1779: [other] WinOS2 apps lost during migration.
* 1688: [booting of CD] Install eCS 2.0 RC 3 in Virtual PC
* 1693: [installer phase 2] eCS 2.0 rc3 hangs loading drivers at phase2
* 1708: [installer phase 2] System hangs
* 1705: [installer phase 2] /APIC not filtered from ACPI.PSD line in phase2
* 1740: [other] MPTS does not work
* 1706: [other] x:\ibmcom\macs contains too many NIF files, causing MPTS to
        fail
* 1695: [other] MPTS crashes after easy install eCS 2.0 rc3
* 1733: [other] ACPI Wizard parameter parsing logic
* 1767: [other] Selective install *still* has OS/2 Warp 4 background and
        titlebar
* 1776: [other] UCLIP locations
* 1775: [other] en_us\ecs\install\install.zip contains a duplicate of itself
* 1758: [installer phase 1] Configure Network page references "Netware"
        instead of "NetWare" and needs additional fixes
* 1759: [installer phase 1] Network types text needs cleaning and consistency
* 1765: [installer phase 2] Disk inactivity warning text
* 1754: [installer phase 1] Language on resistration info page should be
        modified
* 1757: [installer phase 1] Registration screen text needs more polish
* 1751: [other] Unix-like commands in ecs\klibc (coreutils)
* 1761: [installer phase 1] When adding IPX, it is only available for binding
        to the first NIC
* 1742: [other] Couldn't configure MPTS .
* 1684: [other] Scheme Palete doesn't contain a setting for current colors
* 1703: [other] Default locale is still not correctly set during install.
* 1718: [installer phase 2] hang loading BASEDEVs

Updated / added drivers:

* Updated ACPI to revision 3.05
* Updated APM to revision 1.20
* Updated UniAud audiodriver to 1.1.4RC4 release
* Updated JFS code to match eCS Bootable JFS 1.0.7
   The updates for the latest IBM JFS support (14.105) have been merged
   into this release.  It is valid for both HPFS and JFS systems.
* applied IBM APAR PJ31116/PJ31056 Comet Cursor/Suspend (@@fixes 1781)
* samba plugin code at level 3.0.26 @@fixes 1746

=== eComStation 2.0 RC4 README ===

-=# The Christmas 2007 release #=-

!!! WHEN TESTING BETA SOFTWARE, ALWAYS BE SURE TO HAVE A TRIED AND TESTED
    BACKUP OF YOUR SYSTEM !!!

** Netware installation from CD1 **

It is now possible to add Netware client support to eComStation, straight
from the installation CD. This is especially important for those customers
that have a Netware networking environment.


** Preboot harddisk integrity check **

There are several situations which may cause installation problems with LVM
in the install process. In this release, it is possible to disable the
integrity check at page 2 (miscellaneous) of the eComStation installer
preboot menu.

- PBR problems:  Set when either the 'hidden sectors' or the geometry fields
in a bootsector do not match the position of the partition or the used
disk-geometry.

- CHS problems:  Set when the CHS-values in a partition-table for a
  partition do NOT match the current disk-geometry used by the operating
  system.  This may lead to error from (mini)LVM about the disk being
  'corrupt'.  Another possible cause for this error is that if there are
  any partitions present on a disk that have NO LVM information at all,
  and are of a type that gets a default driveletter assigned in that case
  (by OS2LVM.DMD/OS2DASD.CMD)

- Boot problems:  Set when extended-containers are marked ACTIVE, when
  multiple primaries are marked ACTIVE, or if any non-standard flagbyte
  values are used in the partitiontable.  These errors MAY lead to the
  system failing to boot properly!

These will now be detected before the installer starts and an option to fix
them is being presented.  If you choose not to fix them, you are not able
to proceed the installation.

This technology uses a custom DFSee 'engine' and should be safe, however,
neither Serenity Systems International nor Fsys can be held liable for any
damages that may occur to the data on your harddrive.


** Harddisk volume resizing **

This version has a custom DFSee engine that enables reliable RESIZING of FAT32
and NTFS filesystems to allow shrinking an existing Windows installation to
make room for eComStation on the same system.  While this functionality has
been available in DFSee (and the OEM Engine) for quite a while, it was NOT
considered reliable enough to offer to end users during eComStation install.
Starting with DFSee release 7.12, and the OEM Engine based on that, the
reliability of resizing has improved to the point where it can be used
without hesitation for this purpose.  A Windows NTFS filesystem resized by
DFSee will pass a subsequent Windows CHKDSK with NO ERRORS now. The engine
included in RC4 is at level 9.04.

The GUI to this tool has been updated and is now using a graphical interface.
To invoke it, please select 'Paritition Resizing Tool' from the Installation
Volume Manager which can be called during installation (choose 'New Volume'
to start MiniLVM). It will take a while to complete loading, when done,
please select Next to show the list of resizable volumes. If the list is
empty, this means there is no suitable volume detected that has enough free
space for it to be resized.

The GUI has been updated to be more intuitive to the user and will only show
resize panes when there is an actual volume available for resizing. If you
know you have freespace available on your Windows volume, but they do not
show up, you can consider running (multiple times) "defrag" under Windows,
this will rearrange the file layout on disk and may yield in more space
that can be actually freed up. The diskresizer now will show a progress
bar during resizing.

If the entire disk is occupied by a Windows Vista preload installation,
installation of eComStation will not be possible and the installer will
abort (the preboot integrity check will prevent further booting).
You can create freespace on the drive by using the tools supplied by Windows
Vista to manage your disk. In 'FAQ.TXT' a small howto is included.


** Bootable JFS **

This release of eComStation contains the option to install the operating
system on a JFS volume. The advantage of doing this is that the amount of
diskcache is only limited by system memory (typically 10% of available
memory is assigned)
This increased cache size gives a huge gain in overall system performance.
To install onto a Bootable JFS volume, you will have to select 'JFS' as
filesystem type in the 'Format Volume' page of the installer.

A number of analysis tools are available on the install CD:

in \ECS\BOOTJFS

cachejfs.exe   - query and set parameters of cache
cstats.exe     - query usage of cache

in \ECS\BOOTJFS\DEBUG

chklgjfs.exe - show results of last chkdsk
dumpfs.exe   - dump internal structure of JFS
logdump.exe  - dump current state of log to \JFSLOG.DMP
validfs.exe  - show current state of JFS
xchkdmp.exe  - show results from chkdsk.new
xchklog.exe  - dump results of last chkdsk to \chkdsk.new
xpeek.exe    - utility for interactive work with structure of JFS


** Genmac 2.20 RC1 **

This package provides generic driver support for several network interface
cards under OS/2 and eComStation.  Moreover, Genmac is enabled to support WPA
encryption with the Wireless LAN Monitor 3.x or better.

Genmac and the Wireless LAN monitor will be installed when the appropriate
hardware is detected by the installer.  If it is not detected, you can
manually select the driver in the network installation dialog.

Note:  only the selected driver will be copied onto your system, in order to
prevent problems with the MPTS installer later on.  This may seem confusing,
when you run MPTS in a later stage, it will not show all Genmac supported
NICs.

Version 2.20 rc1 of GenMac now supports the NETBEUI protocol.

Version 2.20 rc1 of GenMac now offers suspend & resume on a limited set of network
adapters (when used in conjunction with ACPI) - this is an *experimental*
feature. More details can be found in \ecs\doc\genmac\

Please note that UniAud has known problems with suspend & resume, so if you
want to use this feature, you should not activate the UniAud driver currently.

A full list of supported NIC chipsets can be found in 'WHATSNEW.TXT'.
Support has been added to autodetect over 300 NICs that are using one of
these chipsets.


** ACPI & APM **

Support for ACPI is available in this release.  The current version is 3.05.
ACPI will be automatically enabled if appropriate hardware is detected.
You can manually enable or disable ACPI support at page 4 (USB & ACPI)
of the eComStation installer preboot menu.  Even if not installed, the
corresponding documents are installed on your harddrive. You can find
detailed information and testdocuments in \ECS\DOC\ACPI and \ECS\DOC\APM

Several tests can be performed, please refer to \ECS\DOC\ACPI\TESTER.DOC
and \ECS\DOC\APM\TESTER.DOC

When ACPI is installed, there is a number of utilities from the ACPI
Toolkit you can use, see the list below:

AcpiTree.exe            - Show ACPI tree
ButtonJin.exe           - Wait press Power Button (as demon), GUI
WaitButton.exe          - Wait press Power/Sleep button, VIO
PowerOff.exe            - Power Off (immediate!!)
SetGetThrtl.exe         - Get/Set throtlling CPU
UpTime.exe              - Show uptime via PM Timer
GetValue.exe            - Get current value from PM Timer
AcpiIRQ.exe             - Show current IRQ routing
IrqStat.exe             - Show IRQ calling statistics (SMP only)
SetGetState.exe         - Get/Set frequency/power state
EmbeddedEvent.exe       - Show events from Embedded controllers
GetNotify.exe           - Show notify
Thermal.exe             - Show temperature of thermal zone
ScanPCI.exe             - Show PCI devices
TmrTest.exe             - Test working of timer (testing IRQ0 timer 0)


** multicore CPU support **

This release supports the installation of eComStation on a MultiCore CPU
computer. This includes Intel Core Duo , Core2 Duo and AMD 64 X2.
To enable it, you can do so in the ACPI Wizard that is launched from the
Post Installation tasks at the end of the installation. Alternatively you
can start the ACPI Wizard at any time from the install/remove folder in
the Local System folder on the desktop.

The ACPI Wizard will try to determine your system configuration and set
parameters accordingly. You can manually change them of course.

Please note: many drivers are not SMP capable, which may cause
instability or unexpected behaviour on your system.

For more information please refer to \ECS\DOC\ACPI\ACPI_SMP.DOC


** SMP support **

It is also possible to install eComStation 2.0 RC4 on a regular SMP
machine. You will have to activate it with the ACPI Wizard from the
Post Installation Tasks wizard that is started at the end of the
installation. This should enable you to properly finish installation,
before activating the SMP feature.


** Uninstall SMP support **

It is possible to undo a SMP installation, for example because your system
seems unstable or does not properly function with SMP activated.
For instructions on how to perform uninstallation, please refer to 'FAQ.TXT'
in the root of the CD.


** eComStation Virtual File System (Samba client support) **

Samba is a SMB/CIFS protocols file and print sharing server/client set
originally made for UNIX world to cooperate with corresponding Windows and
OS/2 servers or clients.  eComStation has a native implementation of
SMB/CIFS server/client set - IBM LAN Manager and IBM Peer.  These products
have not been recently updated and may have some compatibility issues with
modern Windows SMB/CIFS implementations.

Serenity Systems International has reached an agreement with Blueprint
Software Works for the inclusion of the 'eComStation Virtual File System'
driver which provides support for Samba Client.  Currently a GUI to
configure it is lacking, but an example of how to mount a Samba resource
can be found in \ECS\DOC\EVFS\REXX

** EVFS GUI **

There now is a GUI that will make it easier to configure network access
using the Samba protocol. There is one big limitation though, the tool
cannot determine if a network connection was properly created - so it
will not provide sensible feedback on that, instead it will always
create a mountpoint which may be empty if the actual connection fails.
The object for this tool is placed in the "Local Network" folder and is
called "Virtual Filesystem for SMB"
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2007.12.28, 09:02:49
Initial Impressions are good. Install goes well under VPC2007, everything works and auto-detects except for the Sound card. Once its up and running, its very much the same in functionality as the previous RCs. I tried the Samba NFS front-end, it seems mostly intuitive, but since I have no other computers on the home network currently, its hard for me to test its usability. I await returning to school and installing on hardware there to test that.
Title: Re: eCS 2.04 RC4
Post by: bjorso on 2007.12.28, 10:53:05

I have tested this release on two laptops and one desktop computer. On my T42p everything is running as expected. This is the first time I try eCS on my Z60M with Widescreen. The only thing I can't get right is graphics, it looks rather ugly but everything else is OK. I'v tried both Panorma and SNAP, no difference. On both laptops I use WiFi and wired LAN through Genmac and it's just great. Niether machine is Dual Core.

The desktop system is a Shuttle and the latest ACPI gives a Kernel trap when running on two CPU kernels. When I use the debug version of ACPI it's working? Chipset and LAN-adapter is VIA, NIC must be set to use IRQ above 15 and that is fixed from the installation in rc4, thanks. Graphics is just fine with Panorama.

Connection to a share on my Samba-server (Debian) works perfect with the new GUI in Networking folder. It's even easier than using Samba from XP. ;D

//bjorso
Title: Re: eCS 2.04 RC4
Post by: DavidG on 2007.12.28, 11:17:27
The graphics on you other laptop, what resolution is it set at?  See what resolution Windows runs at on it and set it to the same resolution using SNAP, provided you can run another resolution besides VGA.  Once done reboot and then go to a command line and type

cd snap <enter>
gaoption lcdusebios off <enter>

reboot system ans see what you have.
Title: Re: eCS 2.04 RC4
Post by: bjorso on 2007.12.28, 12:06:37

The resolution is set to 1680x1050, the same as in Windows XP. Graphics is ATI MOBILITY RADEON X600 and it's detected on page 2 of SNAP settings. The problem is that the virtual screen is bigger than the real screen so I have to scroll to see the edges. Besides that it's looks quite raw compared to the T42p that is perfect on 1600x1200. But that is another chipset, of cource. A reboot after changing lcd bios doesn't change anything I am afraid!

//bjorso
Title: Re: eCS 2.04 RC4
Post by: melf on 2007.12.28, 17:48:37
Quote from: bjorso on 2007.12.28, 10:53:05



Connection to a share on my Samba-server (Debian) works perfect with the new GUI in Networking folder. It's even easier than using Samba from XP. ;D

//bjorso
New GUI works fine here to, easy to use. But, the mounted shares are not possible to save anywhere as I can see. Am I missing something?
Title: Re: eCS 2.04 RC4
Post by: RobertM on 2007.12.28, 21:05:49
Quote from: bjorso on 2007.12.28, 12:06:37

The resolution is set to 1680x1050, the same as in Windows XP. Graphics is ATI MOBILITY RADEON X600 and it's detected on page 2 of SNAP settings. The problem is that the virtual screen is bigger than the real screen so I have to scroll to see the edges. Besides that it's looks quite raw compared to the T42p that is perfect on 1600x1200. But that is another chipset, of cource. A reboot after changing lcd bios doesn't change anything I am afraid!

//bjorso

Hi bjorso,

If the resolution is set correctly, but you have a virtual screen that is larger than the "physical" screen, it means that SNAP is not truly setting the resolution correctly (SNAP is thinking that the physical screen resolution is actually less than what it really is, setting the LCD to that resolution - and assigning the remainder to a virtual area). So for instance in your case, the actual screen resolution the driver may be using is 1280x1024, and assigning the virtual screen 1680x1050 - thus creating a larger virtual screen (and then the hardware is scaling the 1280x1024 viewport to the actual screen resolution). That will be what is causing the ugly screen presentation as eCS is actually sending a lower resolution than the screen wants, and the hardware is scaling the "viewport" to the correct resolution.

I don't know what the solution is to that. I had heard though, that Panorama will work - but there is a configuration option or something similar that you need to edit for it to actually use the widescreen mode. Hopefully someone else here can chime in on how to do that.

-Robert
Title: Re: eCS 2.04 RC4
Post by: melf on 2007.12.28, 23:09:17
Try to ask at panorama forum http://forum.ecomstation.ru/viewforum.php?f=2
Title: Re: eCS 2.04 RC4
Post by: DavidG on 2007.12.29, 00:25:31
Quote from: bjorso on 2007.12.28, 12:06:37

The resolution is set to 1680x1050, the same as in Windows XP. Graphics is ATI MOBILITY RADEON X600 and it's detected on page 2 of SNAP settings. The problem is that the virtual screen is bigger than the real screen so I have to scroll to see the edges. Besides that it's looks quite raw compared to the T42p that is perfect on 1600x1200. But that is another chipset, of cource. A reboot after changing lcd bios doesn't change anything I am afraid!

//bjorso

I have the same video card in my laptop with the exception that my screen resolution is 1440x900.  Always after installing eCS,  I encounter the same problem you have.  The WPS desktop is actually bigger than the screen and I have to move the mouse around to reach the corners of the desktop.

By running the "gaoption lcdusebios off" from the SNAP directory and rebooting, it has always corrected the problem for me.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2007.12.29, 09:19:30
I was very excited today when I got WinXP and eCS to network together without having to jump through hoops, pray to various deities, sacrifice my firstborn, etc etc. All I did was install eCS with NFS, boot it up, log into IBM Peer (Workstation) share something. Then, I went to WinXP and enabled file/folder sharing and just shared the standard Shared Docs folder and my printer objects. Lo and Behold, XP saw eCS and eCS saw XP! I had to do NOTHING. It worked like I dreamt it should, seamless, through the file and folder browser. Amazing. I cant wait to get back to school and hop on my network and see what kind of results I get there.

This was home network, eCS in VirtualPC2007 and WinXP in hardware.
Title: Re: eCS 2.04 RC4
Post by: bjorso on 2007.12.29, 19:55:08
Quote from: melf on 2007.12.28, 17:48:37
New GUI works fine here to, easy to use. But, the mounted shares are not possible to save anywhere as I can see. Am I missing something?

No, you have not missed anything Melf. This GUI is probably only a teaser! It will be more complete in a later version I think.

I tried to log on to my Debian Sambadomain from eCS with the normal requester. It works just fine, the only glitch is a NET8191 message that tells me that it can't find my home directory on the server. That problem is a pure PC problem since eCS can't do shares without calling them something like H: etc. Unix/Linux is not using such things.

I solved it with configuration of an automatic remote share that starts after a successful logon. Use the icon "Sharing and connecting". This will mount your home directory or other shares every time. I can live with the NET8191 message!

On the other hand, the shares are only working well from a tool like FC/2. They don't work from WPS and it seems to be problems with EA's, as expected. It's only useful as a place to store and fetch files for now.

//bjorso
Title: Re: eCS 2.04 RC4
Post by: kim on 2008.01.02, 21:25:58
Quote from: Saijin_Naib on 2007.12.28, 09:02:49Initial Impressions are good. Install goes well under VPC2007, everything works and auto-detects except for the Sound card.

Agree, first impression is very positive; the installation on my ThinkPad T60 (2007-FRG) goes like a charm and everything works fine. No audio still and the Panorama makes the system workable since the SNAP is really a pain to use in VESA mode. Multicore support works well also. So compared with RC3 that I couldn't install at all and compared with the issues that I had with RC2 and now RC4 that installs on 15 minutes it looks great.

One big issue though is that my GPU is getting really hot and I can only assume that Panorama are beating the crap out of it since the fan goes on constantly after a while. That is really a downside.

When looking at the cosmetic wrapping of the eCS I really hope that they spend some time to clean out the old icons since they've now mixed 3 generations of icons within eCS v2.0. There are several individuals here on this forum that have showed that they know how to create great themes and icons; I would suggest the Serenity make use of their skills since they sure could need it.

(http://www.os2world.com/images/stories/2008/systemsetup.gif)
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.02, 21:51:47
Quote from: kimhav on 2008.01.02, 21:25:58

When looking at the cosmetic wrapping of the eCS I really hope that they spend some time to clean out the old icons since they've now mixed 3 generations of icons within eCS v2.0. There are several individuals here on this forum that have showed that they know how to create great themes and icons; I would suggest the Serenity make use of their skills since they sure could need it.

I really agree. They should spend some time to make an overall nice and up to date desktop show up after install. I think it's an underestimated factor attracting new users.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.02, 22:42:00
Its very much underestimated since everyone I show eCS to only remarks on how it looks "old" and basically refuse to give it any further consideration because their initiail impression has already been formed. eSchemes is a step in the right direction, but I think (especially with the Linux crowd) we would need something more like Beryl or Compviz to make the WPS look more modern. Its usability is really quite good, but it looks like its from, well, when its from (1990s).
Title: Re: eCS 2.04 RC4
Post by: kim on 2008.01.03, 11:40:56
Another essential feature for me is the Samba support that seems to work, but misses out a few administrative features with the provided Samba utility. Check following thread (http://www.os2world.com/component/option,com_smf/Itemid,63/topic,628.0/) about the eCS Samba support.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.06, 11:19:01
I would just like to compliment whoever at Mensys or Serenity that upgraded the download server, or did whatever, because I am getting download speeds of upwards of 200kbps consistently, whereas before, 20kbps was a good night. This makes downloading the ISO a much less painful process. Props to whoever fixed whatever, Im liking the phat pipes :D
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.06, 13:58:03
Just got RC4 with NFS and Samba on to my network, and Im not seeing anyone different from before. The same OSX computers and my computer are all that show up. I guess I will wait until more people return, but as of right now, it looks like Im not seeing XP shares anymore :|

Why is it different than home?
Title: Re: eCS 2.04 RC4
Post by: klipp on 2008.01.07, 20:13:15
Could someone please straighten me out! I've installed rc4 on 4 different machines now and the only box that comes up with "Virtual File System for SMB" icon located in the Local Network > Network Utilities window is an ancient Tyan Tomcat IV dual processor motherboard. Running the evfsgui on this machine works fine. Mannually transferring the necessary files and loading the driver in the config.sys of one of the other newer machines throws a Error "Line 9 of Init inevfsgui.VRM: +++ Call EvfsRxLoadFuncs;"
   Thanks for any advice

klipp
Title: Re: eCS 2.04 RC4
Post by: RobertM on 2008.01.07, 22:26:08
klipp,

It could be that:

The most likely problem is the one in GREEN. That simply requires figuring out where the REXX DLL(s) are that are trying to be called and either
(a) moving them to a directory in your LIBPATH statement (such as OS2\DLL) or (better option to avoid clutter)
(b) add the directory where they are located to the LIBPATH statement in your config.sys (terminate the line with a ";")
Title: Re: eCS 2.04 RC4
Post by: klipp on 2008.01.07, 23:50:21
Thank you RobertM you DID "Straighten me out"! I was missing  a dll -- (EVFSCALL.DLL)

klipp
Title: Re: eCS 2.04 RC4 on HP Pavillion dv9000
Post by: kim on 2008.01.11, 09:35:27
Well, gave the latest RC a try on a HP Pavillion DV9000 (PN: GH852EA#UUW) and that didn't work out at all; the first issue was the ACPI-drivers made the system Trap so this has to be disabled. Next issue seems that RC4 isn't able to write or make the changes to the drive structure when asking to make some small changes to the drive. Tried couple of times and everytime rebooting the system it once again asks to make the changes to the drive structure. This change, is that change of MBR?

Also, everything that has to do with virus check, MBR check on bios has been disabled.
Title: Re: eCS 2.04 RC4
Post by: RobertM on 2008.01.11, 10:48:00
Kim,

Is it the Vista or XP version of the dv9000 (I think Vista does something weird with the MBR - though people have managed to overwrite it easily enough with Grub Stage 1, so it shouldnt matter - bringing it up just in case - maybe try "fixing"/removing the MBR with dfSee 9)? And, which hard drive are you installing it to? Perhaps the installer is selecting the wrong drive (and maybe removing one of them to complete the install will thus work)? I had a similar issue with v1.2mr that required wiping the disk - there was something the partition tools would not remove... I thought that was fixed in v2.0rc's though.

Sorry this is all jumbled... really late and I'm beat... hitting the sack. If you cant get it working, I'll try to be more coherent tomorrow...

Night,
Rob
Title: Re: eCS 2.04 RC4
Post by: kim on 2008.01.11, 11:11:01
It's the Vista version of the system and I guess as you say it's the Vista MBR. I'm going to check, assume that it would be easiest to install the Air-Boot on the system to get further on. But I was primary testing the RC4 boot Cd to see the behaviour on this system. It presented a nice Trap E when ACPI was enabled. Not good at all since I had my hope that I wouldn't see any more traps.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.14, 18:00:57
Wow, guys. Strangeness (atleast for me). My current eCS 2.0RC4 install with NFS is actually showing me almost every entry in the Workgroup "Workgroup". Its even showing Vista shares, and I can browse them! It seems the only devices its not showing are uPnP devices like Zune Wireless, x360, Windows Media Center Extender, etc. However, my XP setup has uPnP discovery off as well, so its not seeing them either. eCS however, is missing a few computers from the directory, though I can not find a single common factor among them. I dont know the host OS or any other info, only that they show in Vista/XP but not eCS.

In any case, Im totally amped about this! This is the most sucess I have ever had with the File and Print Resource Browser.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.16, 15:34:08
In the same vein, for some reason I can not see any computers with the File and Print resource browser again. Its only showing 3 entries now, and If I refresh, it will show no more. However, if I right click on one of the computers listed and go to Access Another and check the drop-down, I will sometimes find that a computer that isnt shown will be listed there. Also, If I add a computer manually using this process (like my roommate's share) it will show in the file & print resource browser and work fine. I have deleted all the shown entries using SHIFT+DEL and then refreshed to (to my understanding) have all the entries rebuilt, but its now only showing these 3 entries, and no longer the 30some-40some that it used to (detecting all but uPnP shares). Any hints for me? I have already run checkini many times as I read somewhere on the newsgroup that this may affect whats shown there, but so far, no love.

Edit: I have done a search, and I saw a thread here from last year in which Melf had a similar issue. Was this ever resolved? I am not sure what has changed and why it no longer SHOWS me them, though it clearly can access them through other methods.
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.16, 22:58:44
I don't exactly know which thread you mean. When I was at university about 2 years ago I tried to connect to workgroups there. Succeeded once and never more, gave it up. Here at my home I have had and still have problems to log in. Some periods it just doesn't work and I have not found any solution to that. That refers to the default lan requester.

On the other hand using samba in the EVFS form solves problem nr 2 for me, this always works. Problem is one can't access printers yet. Problem nr 1 I haven't had the oportunity to try, but I guess that will work too.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.17, 07:41:52
Hmm.. It seems like something gets corrupted or changed somewhere in the system because it worked perfectly RIGHT after a fresh install. Right now, it refuses to show more than a few shares, although If i manually add one using Resource Browser it will work. Can anyone help me? I looked at the protocol.ini and it seems okay (but I wouldnt be able to tell anyway :\) and thats the only relevant thing I can think of.

I really want to get this figured out, because I would like to not resort to my standby of reformat/install just to get network shares back properly :C Its got to be something that can be fixed, else it would not work at first!
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.17, 10:36:19
It seems like after every time I run checkini and cleanini and reboot, ONE more (server, some servers have multiple entries as server, server01, server02) is added the the file & print resource broweser, and ONE other share that is NOT listed is added to the access another drop-down, but not shown. O_O

wtf? Help please!

Here is my protocol.ini to start, I don't know what else someone would need to get me in the right direction.

[PROT_MAN]

   DRIVERNAME = PROTMAN$

[IBMLXCFG]

   tcpbeui_nif = tcpbeui.nif
   tcpip_nif = tcpip.nif
   VFET2A_nif = VFET2A.NIF

[NETBIOS]

   DriverName = netbios$
   ADAPTER1 = tcpbeui$,1

[tcpbeui_nif]

   DriverName = tcpbeui$
   Bindings = ,VFET2A_nif
   NODETYPE = "B-Node"
   OS2TRACEMASK = 0x0
   SESSIONS = 130
   NCBS = 225
   NAMES = 21
   SELECTORS = 15
   USEMAXDATAGRAM = "NO"
   NETBIOSTIMEOUT = 500
   NETBIOSRETRIES = 2
   NAMECACHE = 1000
   PURGECACHE = 0
   PRELOADCACHE = "NO"
   NAMESFILE = 0
   DATAGRAMPACKETS = 20
   PACKETS = 50
   ENABLEDNS = 0
   INTERFACERATE = 300

[tcpip_nif]

   DriverName = TCPIP$
   Bindings = VFET2A_nif

[VFET2A_nif]

   DriverName = VFET2A$
   IRQ15OVR = "YES"
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.18, 04:13:06
Frick :C I broke PEER by messing with the Sharing and Connections tool :\ I changed a few of the values in there related to network behavior because some of the values didnt look good (I was reading the help for each item as I did this) and left the values it said to NOT change alone. Following a reboot, PEER will no longer start, and I have to have peer working to use the Sharing and Connections tool :(
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.18, 09:34:39
Well, you always have "Selective install for networking". It didn't work in RC2 and RC3 but I think it is repared in RC4, but not shure though. I guess there are easier ways.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.18, 09:52:10
I donno, I really have to get it working. I used eCS to back up all my valuable files before I formatted my XP drive to get rid of the Trojan Dropper.Agent.GIT virus I had (was in MBR!) but from there, its kinda stuck now :( I cant get peer working to have my friend grab my backup folder from his Vista machine and hold it for me until I reboot to XP and get it back from him. The one JFS recovery tool (for windows) I found is absolute garbage and messes up every file name and extension, rendering the transferred files a little more than totally useless. RSJ seems to support my DVD-burner, but I dont have any DVDs on hand, and the manual says it has a 2gb file-size limit for DVD. Is that 2gb MAX for one file? Or 2gb max for the DVD drive?

I suppose I could use the NTFS read/write experimental IFS driver from the Mensys site, but I am terrified of doing so because it says that it may destroy the files and drive it is using, and I really dont want that.

In any case, any help would be greatly appreciated! This data has survived alot, and I really cant stand to lose my pictures and movies... Its not fair -_-
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.18, 11:54:18
Consider using cdrecord/2-audiocdcreator to burn you dvd:s. In that case you also need dvddao(version 1.0 works with ACDCr, latest versions not, those in between I have not tested). It (dvddao) clearly states in the readme that it correctly writes DVD:s over two GB. I haven't tried that big sizes as I have had no need yet. (Sometimes you get warnings, with ACDCr that it can't estimate free space, but if you know it'll work: just overrule)

I guess you can also use dvddao at commandline basis if your in a hurry and don't want to install new stuff.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.18, 14:53:43
Considering how noob I am at OS/2, I will stick with a GUI tool if there is one available. The goal is to get my files safely back on my NTFS drive and then go to town on eCS and see if I cant get PEER working again, and the File & Print Resource Browser to behave like it did after a fresh install. If it fails, back to a fresh install I go.
Title: Re: eCS 2.04 RC4
Post by: Andi on 2008.01.18, 14:56:02
Don't you have a backup of protocol.ini? On my system there are backup files like protcol.001 and so on. Sometimes backup files are in \ibmlan\install\ too. A "dir \protocol* /s" will find it.

On eCS Systems there's should be an Object in System - Network - Adapter and Protocol. Try this. It's MPTS (for protocol.ini) with a wrapper which corrects ibmlan.ini too.

Next I would try is \ibmlan\install\laninst.exe. It should let you reconfigure peer or even reinstall.

Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.19, 03:28:53
That lanisnt.exe was a strange process whcih resulted in PEER being very much dead still. I finally got my files off (zip tree, put on flash drive, move to friends computer, repeat) and re-installed it. Its nice and clean now and should hopefully stay that way for a while.

I still need some help with the Requester strangeness however.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.19, 06:29:16
Okay, just completed a fresh install. The network requester is backing to being strange. It now only shows me three computers in my Workgroup, myself, and 2 OSX machines. NET VIEW /DOMAIN:WORKGROUP yields the same results. I can not view my room mate using NET VIEW \\Ku.

It gives an error
NET3502: OS/2 error 54 has occurred.
SYS0054: The network is busy or out of resources.

Could this be related to the values that can be set through MPTS for NetBios Over TCP/IP?
Title: Re: eCS 2.04 RC4
Post by: bjorso on 2008.01.19, 16:48:27
Quote from: David Graser on 2007.12.28, 11:17:27
Go to a command line and type

cd snap <enter>
gaoption lcdusebios off <enter>

reboot system ans see what you have.

I did a new install on my Z60m with Widescreen, this time it worked better and the trick with Snap made the screen beeing in correct size and resolution. I don't know why it did not work before?

//bjorso
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.20, 03:50:21
Okay, I am getting a little annoyed here. Please, PLEASE help me out if you have the File & Print Resource Browser working correctly. This is the kind of stuff that will make me never want to use this OS again. Things like how every time I reinstall it acts different, though I install the same things, and reformat every time. Or how some of the classes (multimedia and image) are broken after a fresh install for no good reason, but if you dont install some software will work properly. Or how the File & Print Resource Browser worked ONCE perfectly, but never again, although NOTHING has changed in my hardware environment or network. So again, I BEG of you all, help me with this stuff. It has to do something with the settings in MPTS, of that I am certain. The class issue is something that Serenity should direct their attention to because that is pure and utter bullshit for it not to work correctly if it is installed, I am sorry.
Title: Re: eCS 2.04 RC4
Post by: kim on 2008.01.20, 04:40:33
Quote from: Saijin_Naib on 2008.01.20, 03:50:21
Okay, I am getting a little annoyed here. Please, PLEASE help me out if you have the File & Print Resource Browser working correctly.

Have you reported (http://bugs.ecomstation.nl/login_page.php) the various issues that you've found to SSI? Also to remember that you're running a Release Candidate and not the final version of eCS.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.20, 04:42:41
Yes Kim, I just submitted 5 reports to SSI. And I realize that I am just using the RC, but I still dont see why these issues have not been fixed, because from what I have read, they have been around for a long time.
Title: Re: eCS 2.04 RC4
Post by: kim on 2008.01.20, 05:00:33
I agree that I have had my hopes that some of the issues should have been fixed already since it looks like that next release will be GA. For example the nasty Trap E that I got when testing on a HP laptop wasn't really what I expected to see in this release; we can only cross our fingers that the GA is way better.... and have a more aggressive price. Oh... and we wanted that release yesterday :-)
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.20, 05:06:44
^ lol, I agree. I dont know, I would rather that 2.0 GA is SOLID with all these various issues fixed. My roomate is scared of trying it on his laptop because he sees the issues that I have had with it. I dont know, its a great OS, but the install routine really needs to be fixed so that things work correctly. Also, the File & Print Resource browser should work out of the box, like it did for me that one time. I have yet to get it working correctly again. This is not acceptable.
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.29, 18:45:28
Quote from: Saijin_Naib on 2008.01.16, 15:34:08
In the same vein, for some reason I can not see any computers with the File and Print resource browser again. Its only showing 3 entries now, and If I refresh, it will show no more. However, if I right click on one of the computers listed and go to Access Another and check the drop-down, I will sometimes find that a computer that isnt shown will be listed there. Also, If I add a computer manually using this process (like my roommate's share) it will show in the file & print resource browser and work fine. I have deleted all the shown entries using SHIFT+DEL and then refreshed to (to my understanding) have all the entries rebuilt, but its now only showing these 3 entries, and no longer the 30some-40some that it used to (detecting all but uPnP shares). Any hints for me? I have already run checkini many times as I read somewhere on the newsgroup that this may affect whats shown there, but so far, no love.

Edit: I have done a search, and I saw a thread here from last year in which Melf had a similar issue. Was this ever resolved? I am not sure what has changed and why it no longer SHOWS me them, though it clearly can access them through other methods.


Hi, Brett!
I saw your bugreport at http://bugs.ecomstation.nl/view.php?id=1887 about this "File and print resource browser" issue. You got the tip to set driver parameters B-node to H-node instead, and then you also had to add "Netbios name server adress". Did you get any clue on what adress you should put into that?

I'm interested cause I tried the "H-node" thing on my computer too and I put the adress to my printer server(win2k), that is always on, in the "netbios name server adress" place. Well, I should wait to shout my happiness out, but it really seems to work. My login-problems seems to have disappeared (till I tell the opposite again...). So how have things gone for you?
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.29, 22:11:28
Thus far, I have had no luck as to what value should go in the Netbios Name Server address. I tried doing some research about it and I thought that perhaps my XP share would have the needed values in its hosts and lmanhosts file, but to no avail. The only entry in either file is a null entry of 127.0.0.1 :\ I really am at a loss thus far, and can NOT see how it could have worked properly that one install and not now. I just don't understand.
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.30, 09:45:22
I have these entries in my protocol.ini under [tcpbeui_nif]:

NODETYPE = "H-Node"
NBNSADDR = "192.168.0.142"
NBNSBACKADDR = "192.168.0.115"

where the first adress is to my w2k-computer, which serves as a printer server - and is always on. The other backupadress is to another XP-computer in the network. I got the advice from a betterknowing friend. I don't know if it is correct but so far it still works and let me access my home network at any time (which is very unusual).

I also looked around the net and found people with such problems on MAC in a windows network. The advice was about the same as you got.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.30, 14:44:55
Hmm, okay, that is interesting. I have to find a computer on my network that is always on then. I also have to get their IP addy, which I don't have. What if both addresses I specify are not online? Do I get no LAN results?

Edit:
Okay, so I used the DDNS conifg tool and its saying that my dynamic DNS server for my domian is:
ns-updates.rh.rit.edu

This seems like this would be a Nameserver for the LAN right? So, how do I resolve the IP address from this name address? Is this the value that should go into the Netbios Namserver field? I cant put it in in text because it is too many characters.

Edit Edit:
I put in the IP address that I got from the DHCP configuration tool, maybe it's the same thing?

Edit Edit Edit:
Balls, did not work. I am going to see if I can call my school's IT department and see if they can give me the right stuff.

Edit Edit Edit Edit:
My room mate gave me ns1.rit.edu and ns2.rit.edu from his Ubuntu networking setup. I put those values in and set myself to H-Node and rebooted. During the boot, a whole ton of .os2 files were said to be invalid and not loaded, and upon boot, the network requester had disappeared. Removing the values and rebooting again has restored things.

Edit Edit Edit Edit Edit:
This time I tried using 2 DNS values that XP had specified for itself on my roommates computer. No errors, but now I see nothing on the network browser.
Title: Re: eCS 2.04 RC4
Post by: melf on 2008.01.30, 15:46:25
QuoteHmm, okay, that is interesting. I have to find a computer on my network that is always on then. I also have to get their IP addy, which I don't have. What if both addresses I specify are not online? Do I get no LAN results?

Thought about that to and I don't have an answer. Just fumbling.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.30, 17:21:43
Hmm, the two DNS values from XP are actually the IP of ns1.rit.edu and ns2.rit.edu. I used the GNU toolkit from eCoSoftware to resolve back to IP from hostname and the values match up. Now, I just have to figure out why it still refuses to function correctly.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.30, 22:07:06
Okay, so Ive tried all of these values. These are from my school's IT service. Apparently, we no longer have NetBIOS name servers, and have not had them for a long time. Which makes we wonder how the hell I had it working that one time?

WINS Server: 129.21.3.95 (wins.rit.edu)
Name Server: 129.21.3.17 (ns1.rit.edu)
Name Server: 129.21.4.18 (ns2.rit.edu)
Name Server: 129.21.182.48 (ns.rit.edu)

as my NetBios Name Servers and set myself to H-Node, but nothing works now. I am alone in my own scary corner of the interwebs. I still have internet access courtesey of DHCP, so why the hell cant I browse the workgroups? I thought that DHCP/DDNS handled giving out the Name-server addresses so you get the list of workgroups and clients.
Title: Re: eCS 2.04 RC4
Post by: djcaetano on 2008.01.31, 02:35:02
Quote from: Saijin_Naib on 2008.01.30, 22:07:06
Okay, so Ive tried all of these values. These are from my school's IT service. Apparently, we no longer have NetBIOS name servers, and have not had them for a long time. Which makes we wonder how the hell I had it working that one time?
WINS Server: 129.21.3.95 (wins.rit.edu)

  AFAIK, if truly up and running, WINS Server is able to act like as a NetBIOS Name Server (NBNS).
  I would use this IP as name server for netbios.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.31, 02:50:21
Alright, I will set myself to H-node again and put the WINS server value back in. Can you give me an overview of what my values SHOULD be in that page? I will post a screenshot shortly.

Edit: Screenshot Time
Title: Re: eCS 2.04 RC4
Post by: djcaetano on 2008.01.31, 03:29:13
Quote from: Saijin_Naib on 2008.01.31, 02:50:21
Alright, I will set myself to H-node again and put the WINS server value back in. Can you give me an overview of what my values SHOULD be in that page? I will post a screenshot shortly.
Edit: Screenshot Time

  Well, let me see... I will send you the values I use (I can talk with another WinXP computer in my home network, but it's a point-to-point network, no server):

Node Type: H-Node
Enable SLIP/PP Interface:
NetBIOS Name Server address: [your WINS server]
Backup NetBIOS Name Server address: [your WINS server]
NetBIOS Datagram Distributor address: [your WINS server]
Backup NetBIOS Datagram Distributor address: [your WINS server]
NETBIOS trace level: 0
Maximum Sessions: 225
Maximum Commands: 219
Maximum names: 44
GDT selectors: 15
Full buffer datagrams: NO
Query timeout: 500
NETBIOS retries: 2
Number of names in remote name directory: 1000
Minutes between remote name directory purgues: 0
Preload remote name directory: YES
Maximum number of name-ip address pairs in names file: 100
UDP-frame descriptors: 20
TCP-frame descriptors: 100
Enter NetBIOS Domain Scope String: [your TCP/IP domain name... p.e: aol.com]
Enablement of DNS lookup of RFC-unencoded name: 2
Enter Local NetBIOS Name Scope String: [your NetBIOS/P2P domain name]
Seconds to pause between TCP/IP interface checks: 300

  The most important differences are the domain names that must be added, and the Enablement of DNS lookup equal to 2 (this instructs the protocol to try to resolve names by NetBIOS *and* by TCP/IP DNS). The Preload remote name directory to YES and Maximum number of name-ip address pairs in names file are for using with /IBMCOM/RFCNAMES.LST, something that is very usefull if some machines have always the same IPs... this avoid broadcasting to determine machines and thus reduces the NetBIOS response time.
   There is also /IBMCOM/RFCBCST.LST, where you can define the IPs you want to be broadcasted, limiting the broadcast scope and making things faster.

  In my case, I have a wireless router which acts like a firewall server. My RFCNAMES.LST has only one entry, which has my router IP and its name. This router assigns dynamic IPs for machines in my local network, but this IPs re limited from 192.168.1.100 to 192.168.1.115, whose are listed in /IBMCOM/RFCBCST.LST.

  I don't know if this will solve your problems. It seems to me that some kind of black magic is necessary to make LAN Requester and File and Print Client to talk to Windows machines and domains. I had tried in different configurations with mixed results. In some places I could see everything. In others only could add printers and folders "forcing" them (asking to WPS to create icons). And has been a long time since a Windows could access my computer (the last one was running Win98). I can almost always access WinXP, but WinXP never can do anything with OS/2 shared folders. They are displayed, but when one tries to access it, a password is asked and I never was able to discover it.
  Also, I discovered that WinXP refuses to work with OS/2 Warp Server. Win98 can talk to OS/2 Warp Server (but it needs a lot of tampering with lmhosts file on Win98), but not any Windows NT since Win2k (including XP and, AFAIK, Vista).

  Ah, remember to enable NetBIOS protocol in your WinXP machines (I don't know why, this seems to make things easier) and also to change every appearance of "lmannounce" in your Windows Registry from 0 to 1.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.31, 03:53:02
Thanks for all the info and help! I will try these shortly, but just a quick comment from my end. Its rather strange, my roomate can access my eCS shares perfectly, without issue, from his Vista and XP boxes, with no reg changes, and no netbios enabled! In fact, every other person on the workgroup I asked could see me and access me, and they did not do any tinkering to get it to work. Weird stuff.

Edit:
Two questions:
Enter NetBIOS Name Scope String: (TCP/IP domain name? Where would I find this?)
Enter Local NetBIOS Name Scope String: (Netbios/p2p domain name? What is this?)

Also, does it matter that my IBM OS/2 NetBIOS Over TCP/IP and IBM OS/2 TCP/IP are both set to number 0?
thanks!
Title: Re: eCS 2.04 RC4
Post by: djcaetano on 2008.01.31, 04:59:19
Quote from: Saijin_Naib on 2008.01.31, 03:53:02
Thanks for all the info and help! I will try these shortly, but just a quick comment from my end. Its rather strange, my roomate can access my eCS shares perfectly, without issue, from his Vista and XP boxes, with no reg changes, and no netbios enabled! In fact, every other person on the workgroup I asked could see me and access me, and they did not do any tinkering to get it to work. Weird stuff.

  Very weird.

Quote from: Saijin_Naib on 2008.01.31, 03:53:02
Two questions:
Enter NetBIOS Name Scope String: (TCP/IP domain name? Where would I find this?)

  If your computer is inserted into a TCP/IP network with domain names, then your
computer should have a TCP/IP domain name. For example, my computer is
connect through my provider which is named Virtua. My computer hostname
is SAURON. The TCP/IP domain is virtua.com.br and therefore my computer
can be accessed inside this network using the address sauron.virtua.com.br.
In Windows 98 there was a tab called DNS Configuration on "TCP/IP" properties
with one field called "HOST" (where SAURON would be show, in my computer)
and another field called "DOMAIN" (where virtua.com.br would be shown, in
my computer)

Quote from: Saijin_Naib on 2008.01.31, 03:53:02
Enter Local NetBIOS Name Scope String: (Netbios/p2p domain name? What is this?)

  Usually it is the name of your Workgroup or something like that on Windows.

Quote from: Saijin_Naib on 2008.01.31, 03:53:02
Also, does it matter that my IBM OS/2 NetBIOS Over TCP/IP and IBM OS/2 TCP/IP are both set to number 0?
thanks!

  I had bad experiences on that. Usually you should have NetBIOS over TCP/IP as 0 and NetBIOS as 1. Notice, however, that MPTS Configuration do not update things correctly when changing protocol order. Make a backup of your /IBMCOM/PROTOCOL.INI file befora changing things around. After placing NetBIOS over TCP/IP as 0 and NetBIOS as 1, the following section shoud be present on your PROTOCOL.INI:

[NETBIOS]
   DriverName = netbios$
   ADAPTER1 = tcpbeui$,0
   ADAPTER2 = netbeui$,1

  Notice, however, that MPTS *never* updates the LAN Requester/FPClient. So, look at the file /IBMLAN/IBMLAN.INI and verify that the following is defined:

[networks]
  net1 = TCPBEUI$,0,LM10,34,100,14
  net2 = NETBEUI$,1,LM10,34,100,14

  The important numbers are that following TCPBEUI$ (0, in this case) and NETBEUI$ (1, in this case). They should match the values of PROTOCOL.INI. Also, verify if the following is defined in this IBMLAN.INI:

  wrknets = net1,net2
  Computername = [your computer name]
  Domain = [netbios domain / workgroup]

And...

  srvnets = net1,net2
  SRVCOMMENT = [your computer name]

And also verify if the tag:

  srvhidden = no

  Is set to NO. The default is YES.

Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.31, 06:01:27
Okay, I set Netbios Name Scope string as rh.rit.edu and Local Netbios Name Scope String as Workgroup. ALl other values are set as described, TCP/IP is bound to 0, as is Netbios over TCP/IP. Which should be 1, which should be 0?
Title: Re: eCS 2.04 RC4
Post by: djcaetano on 2008.01.31, 15:21:17
Quote from: Saijin_Naib on 2008.01.31, 06:01:27
Okay, I set Netbios Name Scope string as rh.rit.edu and Local Netbios Name Scope String as Workgroup. ALl other values are set as described, TCP/IP is bound to 0, as is Netbios over TCP/IP. Which should be 1, which should be 0?

  I always place NetBIOS over TCP as 0, and then assign it to net1 on IBMLAN.INI, so NetBIOS over TCP/IP is always 'tried" before plain NetBIOS.
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.31, 22:00:49
Thanks again for the help, but I guess I still have something wrong because its still not working. Do I need Netbios as well as Netbios over TCP/IP and TCP/IP?

Here are my relevant settings windows thus far:
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.01.31, 22:09:05
I put the value WORKGROUP for the Local NetBIOS Name Scope String and rebooted, now I am completely alone on my corner of the network. I cant even see the OSX machines that I could before.

Net View Results:
Title: Re: eCS 2.04 RC4
Post by: RobertM on 2008.01.31, 22:36:00
Saijin,

I dont know if this will help, but I have seen default XP installs that did not "default" to WORKGROUP for a workgroup name. Most recently, I have seen MSHOME (Gateway system) after a format, OEM reinstall.

Go to "Control Panel -> System" and find the appropriate section for computer name, and see what the workgroup name is there and make sure it matches.

If that's not it, then I am not sure...

HTH,
-Rob
Title: Re: eCS 2.04 RC4
Post by: Saijin_Naib on 2008.02.01, 14:37:27
Hey Robert, yeah my XP machine is registered to WORKGROUP because thats what I set it to during the install. I made sure that I registered eCS to the same WORKGROUP when I install it as well. My roomate is registered to WORKGROUP under XP, and MSHOME under Ubuntu, and he can see me easily either way. Its just I cant see going out. I must not be getting the list of names, but clearly I am broadcasting out to everyone else. Networking, like many other things, is completely over my head -_-