Author Topic: eWorkplace ini file entries?  (Read 8126 times)

Pete

  • Hero Member
  • *****
  • Posts: 1281
  • Karma: +9/-0
    • View Profile
eWorkplace ini file entries?
« on: January 28, 2019, 05:36:53 am »
Hi All

I've been doing a little updating to USBcfg and decided to add the option to reboot when saving changes.

Rather than reinvent the wheel I thought I'd use the XWorplace Shutdown - xshutdwn.cmd - if XWorkplace is installed with a "fallback" of using the standard system shutdown for non-XWorkplace users.

The above works in my limited testing but the thought occurs:
I am reading the os2.ini Application: XWorkplace, Key: XFolderPath to locate the XWorkplace installed directory. Does eWorkplace (The eCS cutdown version of XWorkplace) use the same os2.ini Application/Key entries? - And does that apply to any cutdown version installed by ArcaOS?


Regards

Pete

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: eWorkplace ini file entries?
« Reply #1 on: January 28, 2019, 06:48:48 am »
Quote
And does that apply to any cutdown version installed by ArcaOS?

ArcaOS, cut down version (as you put it), uses that key. I no longer have an eCS system handy, so I can't say for sure, but I think eWorkplace uses the same key.

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: eWorkplace ini file entries?
« Reply #2 on: January 28, 2019, 07:10:23 am »
Be warned, thet the order of CONFIG.SYS entries is changing, with Arca Noae USB stack 12.1, and later.

USBD.SYS must come after the USB?HCD entries, like this:

Code: [Select]
BASEDEV=USBOHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBD.SYS
BASEDEV=USBHID.SYS

if the stack is older, and they must be like this:

Code: [Select]
BASEDEV=USBD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBHID.SYS

if the USB stack is version 12.1, or later (I am told):

Ian Manners

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 464
  • Karma: +10/-0
  • I am the computer, it is me.
    • View Profile
    • ComKal Networks Australia
Re: eWorkplace ini file entries?
« Reply #3 on: January 28, 2019, 03:28:56 pm »
Hi Doug,

Checked my config.sys on a whim, the order I have is:

  BASEDEV=USBxHCD.SYS
  BASEDEV=USBEHCD.SYS
  BASEDEV=USBD.SYS
  BASEDEV=USBHID.SYS
 
Server has the same order, been like that for many years.
I'll check the readme if I get the 12.x's :)
Cheers
Ian B Manners

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: eWorkplace ini file entries?
« Reply #4 on: January 28, 2019, 04:30:16 pm »
Yes, all versions (XWP, eWPS and XWPS) use the same ini keys.

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: eWorkplace ini file entries?
« Reply #5 on: January 28, 2019, 07:52:06 pm »
Quote
Server has the same order, been like that for many years.
I'll check the readme if I get the 12.x's :)

The installer will correct the order, when you install it, but other things may change it back (because that has always been the way it was done). You will get errors during boot, if it is wrong (either way).

I will note, that LCSS (Logical Config.Sys Sort) has been modified to handle the situation correctly, but only when booted from the same system where USB 12.1+ is installed (I need to do more changes to try to better handle that).

Pete

  • Hero Member
  • *****
  • Posts: 1281
  • Karma: +9/-0
    • View Profile
Re: eWorkplace ini file entries?
« Reply #6 on: January 28, 2019, 08:17:27 pm »
Hi All

Thanks for responses re: ini file entries.

@Ian
How many years have you been running a usb3 driver?
I suspect "BASEDEV=USBxHCD.SYS" is a case of replace "x" with either "U" or "O"

@Doug
Just to confirm: For usb12.1 or later USBcfg output should arrange the usb drivers with usbd.sys as the first line?


Regards

Pete

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: eWorkplace ini file entries?
« Reply #7 on: January 28, 2019, 08:23:50 pm »
Quote
Just to confirm: For usb12.1 or later USBcfg output should arrange the usb drivers with usbd.sys as the first line?

That is what I have been told.

ivan

  • Hero Member
  • *****
  • Posts: 1558
  • Karma: +17/-0
    • View Profile
Re: eWorkplace ini file entries?
« Reply #8 on: January 28, 2019, 09:41:08 pm »
Hi Pete,

Ian is most probably running the mythical USB3.0 driver we have heard about for the last few years and if that is so I would like to know what hardware it is running on (most probably Intel processors so Ryzen misses out again).

Pete

  • Hero Member
  • *****
  • Posts: 1281
  • Karma: +9/-0
    • View Profile
Re: eWorkplace ini file entries?
« Reply #9 on: January 29, 2019, 10:23:28 pm »
Hi ivan

Ian is most probably running the mythical USB3.0 driver we have heard about for the last few years

Be nice to know it has been thoroughly tested  ;-)

Hopefully the real USB3 drivers will arrive soon...

As to whether they will work on an AMD Ryzen we will leave that to you to discover  :-)

I seem to recall you have had various driver problems with AMD cpu based systems over the years which I seem to have mainly avoided though all my Desktop systems have been AMD based since around the mid 1990s.

I have not - yet - built a Ryzen cpu based system. Hopefully you will have all the problems sorted before I have a go later this year  :-)


Regards

Pete



ivan

  • Hero Member
  • *****
  • Posts: 1558
  • Karma: +17/-0
    • View Profile
Re: eWorkplace ini file entries?
« Reply #10 on: January 30, 2019, 08:57:02 pm »
Hi Pete,

Like you I have always used AMD processors since they were first available, Even the HP DL-385 server down in the garage has a pair of dual core Opteron 280 processors.

I think that many of the problems I have encountered with AMD based equipment has been because I have tried to use the cutting edge AMD processors with an operating system that hasn't got there at the time.  Once the drivers catch up I have very stable OS/2 systems.

At the moment we are limited with the Ryzen (AM4 socketed) motherboards because we don't have USB 3.0 drivers and are therefore limited to MBs having PS/2 keyboard and mouse sockets or a combined KB/Mouse PS/2 socket with USB adapters or Y cable.
The other stumbling block is the installer doesn't want to work, gives a 'not enough memory' error but there are ways around that.