Feed for discussion General in project QNX RTOS v4 [EOL].

post122405: Unable to download larger files from community.qnx.com

2023-10-22T16:07:26Z

Hi all,

I'm desperately trying to download the last QNX 4.25 Install ISO (2015), but it seems the server @community.qnx.com has an issue, misconfiguration or is deliberately terminating connections right around 12 seconds in.

Regardless from where I try it (4 different ISP, 3 in germany, 1 in Italy, from my mobile network, over HTTPS proxy located in the US, 2 different browsers and CURL...), the connection is always terminated ~12s after the download starts. So, depending on the DL speed (I never got more than 11MB/s, even on Multi-GBit lines), I never get more than 110MB of this file - and the server does not accept a "range" request to continue the aborted download.

Is someone else experiencing this? Any way to raise the issue with BB if it's not intentional?

Or is there another server than 209.226.137.8 available to serve this request or another method like FTP?

Thanks!

- Robin

post122205: Re: CompactFlash disk corruption, possible relation to popen or Pipe?

2023-04-10T18:04:28Z

One other piece of information in case it is helpful:

Most of the nodes are running the following parameters for Fsys:

/bin/Fsys -Hdisk## -A -r8000

Where ## is the size of the CompactFlash card.

Some of the nodes (not sure if it's related, but these nodes have only seen a corrupt file like awk rather than unbootable drives) are running with:

/bin/Fsys -d0 -c0k -A -r 8000

post122204: CompactFlash disk corruption, possible relation to popen or Pipe?

2023-04-10T17:53:53Z

Hi all,

We are experiencing production issues with drives running QNX 4.25 with CompactFlash cards (solid state) as the disk for the node.  We are seeing multiple failure modes.  What we are frequently seeing is that when the nodes are rebooted/power cycled the node won't reboot and gives a message of "Reboot and select proper boot device" - the drive is unbootable.  We've also seen issues where the node is online but some files on the disk are corrupted (an example is awk, the program would crash when you attempt to run it and its checksum does not match other nodes in the system).  We've also seen issues where trying to run a program (example: netinfo), or access a file will give a "Input/output error".  Additionally, we sometimes see error messages in terminal 1: "popen: Input/output error".  Sometimes we see a combination of these failure modes, sometimes we just see one, we have yet to see a repeatable pattern.

Our application does use a popen() call to execute some shell commands and get the result back into the program.  That particular code runs on a loop and executes roughly every 1 second.

In most cases we see some errors in chkfsys, especially after the nodes have had problems.  The amount of errors varies.  In some of the nodes that are completely unbootable we've been able to mount them as an external drive via io-usb and a USB-to-CompactFlash adapter.  Some of them don't mount, but some do.  The ones that do mount successfully typically show a very large number of errors when running chkfsys.

These failures have occurred on multiple different cards in multiple different nodes.  As far as we can tell the cards are not worn out or having hardware issues/bad sectors.  Most of these cards are not very old, which also leads us to think this isn't a hardware failure in the CompactFlash cards themselves.

One thing we noticed when investigating is that the Pipe manager (/bin/Pipe) is not running on these nodes.  We're not sure if that is related or not.  We read in the help manual that when the Pipe manager is not running that pipes are implemented through the Fsys driver, but we're not sure if that is having an impact or not either.  We are starting to suspect that the issue may be tied either to Pipe, popen, Fsys driver parameters, or some combination of these.  We also have some suspicions that there may be a correlation with the processor board, since many of these nodes run on a dual-core Intel Core 2 Duo.  Some of them run on boards with a single-core Pentium processor, but we haven't seen any issues where the nodes won't reboot on the Pentium processors, just individual files being corrupt (i.e a bad checksum for /bin/awk).  We're not sure if maybe the Fsys driver behaves badly with a dual-core processor or not.

There are a mix of versions across the field, some are runnign /bin/Fsys version 4.24V, some are running 4.24Z.  Some are running /bin/Fsys.eide (some are version 4.25A, some are 4.25G), some are running /bin/Fsys.atapi version 4.25G.  All are running /boot/sys/Proc32 4.25Q.

If anyone out there has any ideas or can help us, we would be greatly appreciative.

post121780: Re: 2 Port PCI Serial Card

2022-04-13T08:11:18Z

QNX is 4.25

post121779: 2 Port PCI Serial Card

2022-04-13T08:10:11Z

Hello.

I have installed an 2 port pci serial card , and i want to know how can i initialise it and use it.

I have attached a photo of the installation.

post121762: Sample Network Driver

2022-03-14T16:56:30Z

HI All

I wondered would anyone have any information on writing a network driver for QNX and what it would need to interface to such as Net. Or better yet would anyone have a sample driver they may be able to share?

BEst Regards

Paul

post121632: Pentium Dual Core G4400

2021-10-25T09:47:15Z

Hello,

I'm thinking of using the following PC ...

SIMATIC IPC347G (rack PC, 19",

4 U); Pentium Dual Core G4400

(2C/2T, 3.3 GHz, 3 MB cache)

Any ideas whether it is compatible?

Regards,

Pete

post121599: Re: Utopia font

2021-09-22T12:41:34Z

You can look up fonts on https://upfonts.com/liberator-font/ . You might find something better there. You can even try to make your font if you can work even a bit in photoshop. Nowadays, fonts are required everywhere. Many companies are paying a lot of money to get their personal fonts with the rights on them. It can bring them a lot of money in the future and even save more. Since using a font in the logo, creation has to be approved and paid for to the person who has the rights on it.

post121598: TSHARC Touch Screen driver for Photon/Input

2021-09-20T06:34:16Z

Does anyone know which of the touchscreen drivers would work with the 4 byte protocol used by the Microchip TSHARC-12o touch screen board.

There are a few options for Input, but so far no luck.

If I cat the input on the serial port and touch the touch screen I can see the data, I have recorded some of the data and the format is correct, so I am confident I have the right baud rate.

I just don't know if any of the touchscreen options actually use the 4 byte format.

Thanks,

John

post121597: Re: AMD HD6250 Graphics

2021-09-20T06:30:12Z

Solved this issue. Added -cnone -nnone and -r switches to the vesabios.ms mode switcher in the crttrap.list file and now it doesn't crash when running the switcher.

post121596: AMD HD6250 Graphics

2021-09-18T05:41:05Z

Hi,

I am trying to find a suitable graphics mode for Photon on a Advantech PCM-9376 SBC

When I run vesabios.trap, it detects a few modes and then after 320x200x8 (i0x13) it crashes with a segmentation fault at 0005:00010C95

It has a TTL display output that I am using which only supports up to 1024x600.

I don't know if the issue is with the resolution or with the BIOS not being fully compatible with 386 protected mode, as this was certainly the problem with Fsys that meant I had to use the Proc32 with the -E0 option to stop Fsys.atapi from crashing (a big thank you to whoever made that work around for Proc32).

I only need 640x480 with 16, 24 or 32 bit colour for the display.

Is there any way that I can set up my crt trap file without relying on the trapper to acheive this?

I'm not sure how to go about working out all the command line switches that the driver needs.

Thanks in advance,

John

post121510: Re: QNX 4.25 2015 Experimental USB

2021-07-15T11:19:00Z

Hi Voicu,

Try following commands:

# cd /boot

# buildqnx -v build/install.2 images/install.2

where build/install.2 is your build file and images/install.2 is created boot image.

Keep in mind that you do not need to launch Fsys directly. Instead this you have to modify Fsys line in your build/install.2 build file.

Respectfully,

Oleg

> Hello Oleg

>

> When i try to run the buildqnx -v on install.2 it says line length exceded >

> 500

>

> If i try to write Fsys -r 500 it says "cant attach name , resource name busy"

>

post121508: Re: QNX 4.25 2015 Experimental USB

2021-07-14T10:06:57Z

Hello Oleg

When i try to run the buildqnx -v on install.2 it says line length exceded >500

If i try to write Fsys -r 500 it says "cant attach name , resource name busy"

post121504: Re: QNX 4.25 2015 Experimental USB

2021-07-06T18:31:26Z

And I do not see the -r 500 at Fsys line.

> and here is OS Build file (or install.2 from boot/builds)

>

> /boot/sys/boot

> $ /boot/sys/boot -v

>

> /boot/sys/Proc32

> $ /boot/sys/Proc32 -E0 -l 2

>

> /boot/sys/Slib32

> $ /boot/sys/Slib32

>

> /boot/sys/Slib16

> $ /boot/sys/Slib16

>

> /boot/Fsys

> $ /boot/Fsys -Hdisk160

>

> /boot/Fsys.ahci

> $ /boot/Fsys fsys -Ndsk1 -n0-hd1. -n5=cd1.

>

> /boot/mount

> $ /boot/mount -p /dev/hd1.0 /dev/hd1.ot77 /

>

> /boot/sinit

> $ /boot/sinit TERM=qnxm

post121503: Re: QNX 4.25 2015 Experimental USB

2021-07-06T18:30:33Z

Hi Voicu,

Please, read the documentation about it. Or provide output of make command (if you use ) in verbose mode.

Respectfully,

Oleg

> i dont know how to use the buildqnx -v command (it asks for a filename)

post121502: Re: QNX 4.25 2015 Experimental USB

2021-07-06T12:51:34Z

and here is OS Build file (or install.2 from boot/builds)

/boot/sys/boot

$ /boot/sys/boot -v

/boot/sys/Proc32

$ /boot/sys/Proc32 -E0 -l 2

/boot/sys/Slib32

$ /boot/sys/Slib32

/boot/sys/Slib16

$ /boot/sys/Slib16

/boot/Fsys

$ /boot/Fsys -Hdisk160

/boot/Fsys.ahci

$ /boot/Fsys fsys -Ndsk1 -n0-hd1. -n5=cd1.

/boot/mount

$ /boot/mount -p /dev/hd1.0 /dev/hd1.ot77 /

/boot/sinit

$ /boot/sinit TERM=qnxm

post121501: Re: QNX 4.25 2015 Experimental USB

2021-07-06T12:47:31Z

here is my sysinit.2

#image: /boot/sys/boot -v

#image:/boot/sys/Proce32 -E0 -| 2

#image:/boot/sys/Slib32

#image:/boot/sys/Slib16

#image:/bin/Fsys -Hdisk160

#image:/bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

#image:/bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

#image:/bin/sinit TERM=qnxm

#export NODE=2

export KBD=en_CA_101.kbd

export ABLANG=en

export CON_KBD=USA

export TZ=est05edt04,M4.1.0/2,M10.5.0/2

/bin/rtc -| hw

Dev &

emu87 &

Pipe &

/bin/Dev.ser -N/dev/ser1 3f8,4 &

/bin/Dev.ser -N/dev/ser1 2f8,3 &

io-usb

devu-kbd

Dev.ansi -Q -n6 -d /dev/usbkbd0 &

reopen /dev/con1

kbd $CON_KBD

prefix -A/dev/console=/dev/con1

Dev.pty &

Dev.pty -n16 &

/bin/Fsys.umass fsys -Ndsk2 -n0=hd2. -n5=cd2.

Iso9660fsys /cd2.0=/dev/cd2.0 &

#Define the default CD Rom

/bin/prefix -A /cd=//0/cd2.0

nameloc &

chkfsys /

if test -f /etc/config/bin/tcpip.$NODE

then

/etc/config/bin/ph.$NODE

else

tinit -t/dev/con1 &

tinit -T/dev/con2[2-6] &

fi

post121500: Re: QNX 4.25 2015 Experimental USB

2021-07-06T12:46:45Z

i dont know how to use the buildqnx -v command (it asks for a filename)

post121493: Re: QNX 4.25 2015 Experimental USB

2021-07-05T09:37:54Z

Hi Voicu,

I've just tried the same and booting is fine with /dev/ram created. Can you attach here your build file and output buildqnx -v command.

Respectfully,

Oleg

> If i write on the same line with -Hdisk160 -r500 the system hangs

post121492: Re: QNX 4.25 2015 Experimental USB

2021-07-05T05:45:44Z

If i write on the same line with -Hdisk160 -r500 the system hangs

post121489: Re: QNX 4.25 2015 Experimental USB

2021-07-02T16:31:19Z

/bin/Fsys

$ /bin/Fsys -Hdisk160 -r500

I made a mistake then , cause i wrote it like that but i put a space between -r and 500

So the correct form is $ /bin/Fsys -Hdisk160 -r500 or $ /bin/Fsys -Hdisk160 -r 500 ?

post121486: Re: QNX 4.25 2015 Experimental USB

2021-07-02T10:52:03Z

It should be:

/bin/Fsys

$ /bin/Fsys -Hdisk160 -r500

Respectfully,

Oleg

> Fsys failed to attach name: resource busy.

>

> And this is the content of my install.2

>

> /boot/sys/boot

> $ /boot/sys/boot -v

>

> /boot/sys/Proc32

> $ /boot/sys/Proc32 -E0 - l 2

>

> /boot/sys/Slib32

> $ /boot/sys/Slib32

>

> /boot/sys/Slib16

> $ /boot/sys/Slib16

>

> /bin/Fsys

> $ /bin/Fsys -r 500

>

> /bin/Fsys

> $ /bin/Fsys -Hdisk160

>

> /bin/Fsys.ahci

> $ /bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

>

> /bin/mount

> $ /bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

>

> /bin/sinit

> $ /bin/sinit TERM=qnxm

>

post121485: Re: QNX 4.25 2015 Experimental USB

2021-07-02T10:51:02Z

Voicu,

Do not launch Fsys twice. You have to add desired options to the single Fsys line.

Respectfully,

Oleg

> I understand , but where do i have to write the Fsys -r command?

> I tried like this.

> i edited the install.2 of the pc, and added the line

>

> /bin/Fsys

> $ Fsys -r 500

>

> then i compiled the file with make b=install.2

> i copied the install.2 as .altboot , so it wouldnt mess with the original boot

>

> And i get the error that Fsys resource busy

post121484: Re: QNX 4.25 2015 Experimental USB

2021-07-02T10:48:39Z

Fsys failed to attach name: resource busy.

And this is the content of my install.2

/boot/sys/boot

$ /boot/sys/boot -v

/boot/sys/Proc32

$ /boot/sys/Proc32 -E0 - l 2

/boot/sys/Slib32

$ /boot/sys/Slib32

/boot/sys/Slib16

$ /boot/sys/Slib16

/bin/Fsys

$ /bin/Fsys -r 500

/bin/Fsys

$ /bin/Fsys -Hdisk160

/bin/Fsys.ahci

$ /bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

/bin/mount

$ /bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

/bin/sinit

$ /bin/sinit TERM=qnxm

post121483: Re: QNX 4.25 2015 Experimental USB

2021-07-02T10:37:43Z

I understand , but where do i have to write the Fsys -r command?

I tried like this.

i edited the install.2 of the pc, and added the line

/bin/Fsys

$ Fsys -r 500

then i compiled the file with make b=install.2

i copied the install.2 as .altboot , so it wouldnt mess with the original boot

And i get the error that Fsys resource busy

post121482: Re: QNX 4.25 2015 Experimental USB

2021-07-02T09:12:42Z

Hi Voicu,

You can use Fsys's -r option to create RAM-disk. If it doesn't work then post here the output of command.

Also you can use Efsys.ram to create embedded filesystem on ram disk.

Respectfully,

Oleg

> Long story short is i need to make a ramdisk called /ram.

> What lines and where do i have to write to make it work ?

post121481: Re: QNX 4.25 2015 Experimental USB

2021-07-02T07:16:59Z

Long story short is i need to make a ramdisk called /ram.

What lines and where do i have to write to make it work ?

post121479: Re: QNX 4.25 2015 Experimental USB

2021-07-01T20:33:20Z

I forgot to mention in the post that i wrote -r 500 like it was on the old hardware. (on the old hardware it created the /dev/ram /ram and it worked)

Should i use another value?

post121478: Re: QNX 4.25 2015 Experimental USB

2021-07-01T13:49:28Z

Hi Voicu,

It looks like you have forgotten to specify argument for -r option.

Respectfully,

Oleg

> Hello dear Oleg!

> I have another issue.

> I need to create a ramdisk /dev/ram but when i try it the system boots and

> hangs.

> i write

> /BIN/FSYS

> $ Fsys -Hdisk160 -r

>

> and it doesnt work.

> On the old hardware that doesnt work anymore the line was

> /BIN/FSYS

> $ Fsys -r 500

> dinit /dev/ram /ram

>

> and it worked. (The old hardware had IDE HDD)

> This one has a CF.

> What should i do ?

>

>

>

post121477: Re: QNX 4.25 2015 Experimental USB

2021-07-01T13:36:05Z

Hello dear Oleg!

I have another issue.

I need to create a ramdisk /dev/ram but when i try it the system boots and hangs.

i write

/BIN/FSYS

$ Fsys -Hdisk160 -r

and it doesnt work.

On the old hardware that doesnt work anymore the line was

/BIN/FSYS

$ Fsys -r 500

dinit /dev/ram /ram

and it worked. (The old hardware had IDE HDD)

This one has a CF.

What should i do ?

post121461: Re: Hard Drive failures

2021-06-18T08:34:16Z

Hi Niraj,

QNX 4 does not support TRIM or similar technologies. And I didn't hear before about such technologies for Mag drives. If it possible customer should use software which work with disk more sparingly (decrease read and write operations, write is more significant here). Also customer may use industrial disks which provide more longer life cycle.

Respectfully,

Oleg

> A customer is asking below questions.

> They are facing too many computer failures related hard drives.

> 1. Does QNX4 support any trim function or equivalent? If there is an

> equivalent function what is it?

> 2. Does not having this function shorten the life of SSD?

> 3. Is there an equivalent function to be run on a Mag drive which enhances the

> lifespan of a Mag drive?

post121460: Hard Drive failures

2021-06-18T00:14:39Z

A customer is asking below questions.

They are facing too many computer failures related hard drives.

1. Does QNX4 support any trim function or equivalent? If there is an equivalent function what is it?

2. Does not having this function shorten the life of SSD?

3. Is there an equivalent function to be run on a Mag drive which enhances the lifespan of a Mag drive?

post121387: Re: QNX 4.25 2015 Experimental USB

2021-04-22T09:05:04Z

Hi Voicu,

Fsys.umass should support USB floppy devices.

Respectfully,

Oleg

> Hey thanks for the solution, it worked. I have one more question .

> If i want to attach an USB - Floppy Disk what do i have to write in the

> sysinit ?

> Thanks!!!!

post121386: Re: QNX 4.25 2015 Experimental USB

2021-04-22T07:10:51Z

Hey thanks for the solution, it worked. I have one more question .

If i want to attach an USB - Floppy Disk what do i have to write in the sysinit ?

Thanks!!!!

post121384: Re: QNX 4.25 2015 Experimental USB

2021-04-21T08:27:37Z

Hi Voicu,

Yes, I meant something like this.

I see that you launch io-usb twice. Remove second io-usb (before Fsys.umass).

Respectfully,

Oleg

> You mean that my sysinit should look like this ?

>

> #image: /boot/sys/boot -v

> #image:/boot/sys/Proce32 -E0 -| 2

> #image:/boot/sys/Slib32

> #image:/boot/sys/Slib16

> #image:/bin/Fsys -Hdisk160

> #image:/bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

> #image:/bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

> #image:/bin/sinit TERM=qnxm

> #export NODE=2

> export KBD=en_CA_101.kbd

> export ABLANG=en

> export CON_KBD=USA

> export TZ=est05edt04,M4.1.0/2,M10.5.0/2

> /bin/rtc -| hw

> Dev &

> emu87 &

> Pipe &

> /bin/Dev.ser -N/dev/ser1 3f8,4 &

> /bin/Dev.ser -N/dev/ser1 2f8,3 &

> io-usb

> devu-kbd

> Dev.ansi -Q -n6 -d /dev/usbkbd0 &

> reopen /dev/con1

> kbd $CON_KBD

> prefix -A/dev/console=/dev/con1

> Dev.pty &

> Dev.pty -n16 &

> io-usb

> /bin/Fsys.umass fsys -Ndsk2 -n0=hd2. -n5=cd2.

> Iso9660fsys /cd2.0=/dev/cd2.0 &

> #Define the default CD Rom

> /bin/prefix -A /cd=//0/cd2.0

> nameloc &

> chkfsys /

> if test -f /etc/config/bin/tcpip.$NODE

> then

> /etc/config/bin/ph.$NODE

> else

> tinit -t/dev/con1 &

> tinit -T/dev/con2[2-6] &

> fi

post121383: Re: QNX 4.25 2015 Experimental USB

2021-04-20T20:32:59Z

You mean that my sysinit should look like this ?

#image: /boot/sys/boot -v

#image:/boot/sys/Proce32 -E0 -| 2

#image:/boot/sys/Slib32

#image:/boot/sys/Slib16

#image:/bin/Fsys -Hdisk160

#image:/bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

#image:/bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

#image:/bin/sinit TERM=qnxm

#export NODE=2

export KBD=en_CA_101.kbd

export ABLANG=en

export CON_KBD=USA

export TZ=est05edt04,M4.1.0/2,M10.5.0/2

/bin/rtc -| hw

Dev &

emu87 &

Pipe &

/bin/Dev.ser -N/dev/ser1 3f8,4 &

/bin/Dev.ser -N/dev/ser1 2f8,3 &

io-usb

devu-kbd

Dev.ansi -Q -n6 -d /dev/usbkbd0 &

reopen /dev/con1

kbd $CON_KBD

prefix -A/dev/console=/dev/con1

Dev.pty &

Dev.pty -n16 &

io-usb

/bin/Fsys.umass fsys -Ndsk2 -n0=hd2. -n5=cd2.

Iso9660fsys /cd2.0=/dev/cd2.0 &

#Define the default CD Rom

/bin/prefix -A /cd=//0/cd2.0

nameloc &

chkfsys /

if test -f /etc/config/bin/tcpip.$NODE

then

/etc/config/bin/ph.$NODE

else

tinit -t/dev/con1 &

tinit -T/dev/con2[2-6] &

fi

post121370: Re: QNX 4.25 2015 Experimental USB

2021-04-07T08:39:25Z

Hi Voicu,

Dev.ansi should have -d option to support USB keyboard. Please check use Dev.ansi for that. To use native (not in USB legacy mode) USB keyboard in console you have to add (or replace existing ones) lines in specified order (usually add io-usb and devu-kbd just before the Dev.ansi) to you /etc/config/sysinit.N file:

io-usb

devu-kbd

Dev.ansi -Q -n6 -d /dev/usbkbd0 &

Additionally adding sleep 1, sleep 2 or so on may be required to be sure that io-usb and devu-kbd are both started and initialized before the launching of Dev.ansi.

The -d option is significant here. Also if you launch io-usb and devu-kbd after the Dev.ansi without -d option then the keyboard will leave the USB legacy mode and stop to working.

Respectfully,

Oleg

> > Here is my sysinit

> >

> > #image: /boot/sys/boot -v

> > #image:/boot/sys/Proce32 -E0 -| 2

> > #image:/boot/sys/Slib32

> > #image:/boot/sys/Slib16

> > #image:/bin/Fsys -Hdisk160

> > #image:/bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

> > #image:/bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

> > #image:/bin/sinit TERM=qnxm

> > #export NODE=2

> > export KBD=en_CA_101.kbd

> > export ABLANG=en

> > export CON_KBD=USA

> > export TZ=est05edt04,M4.1.0/2,M10.5.0/2

> > /bin/rtc -| hw

> > Dev &

> > emu87 &

> > Pipe &

> > /bin/Dev.ser -N/dev/ser1 3f8,4 &

> > /bin/Dev.ser -N/dev/ser1 2f8,3 &

> > Dev.ansi -Q -n6 &

> > reopen /dev/con1

> > kbd $CON_KBD

> > prefix -A/dev/console=/dev/con1

> > Dev.pty &

> > Dev.pty -n16 &

> > io-usb

> > /bin/Fsys.umass fsys -Ndsk2 -n0=hd2. -n5=cd2.

> > Iso9660fsys /cd2.0=/dev/cd2.0 &

> > #Define the default CD Rom

> > /bin/prefix -A /cd=//0/cd2.0

> > nameloc &

> > chkfsys /

> > if test -f /etc/config/bin/tcpip.$NODE

> > then

> > /etc/config/bin/ph.$NODE

> > else

> > tinit -t/dev/con1 &

> > tinit -T/dev/con2[2-6] &

> > fi

>

> If i take out the io-usb the keyboard works , else it freezes.

post121367: Re: QNX 4.25 2015 Experimental USB

2021-04-06T08:14:01Z

> Here is my sysinit

>

> #image: /boot/sys/boot -v

> #image:/boot/sys/Proce32 -E0 -| 2

> #image:/boot/sys/Slib32

> #image:/boot/sys/Slib16

> #image:/bin/Fsys -Hdisk160

> #image:/bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

> #image:/bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

> #image:/bin/sinit TERM=qnxm

> #export NODE=2

> export KBD=en_CA_101.kbd

> export ABLANG=en

> export CON_KBD=USA

> export TZ=est05edt04,M4.1.0/2,M10.5.0/2

> /bin/rtc -| hw

> Dev &

> emu87 &

> Pipe &

> /bin/Dev.ser -N/dev/ser1 3f8,4 &

> /bin/Dev.ser -N/dev/ser1 2f8,3 &

> Dev.ansi -Q -n6 &

> reopen /dev/con1

> kbd $CON_KBD

> prefix -A/dev/console=/dev/con1

> Dev.pty &

> Dev.pty -n16 &

> io-usb

> /bin/Fsys.umass fsys -Ndsk2 -n0=hd2. -n5=cd2.

> Iso9660fsys /cd2.0=/dev/cd2.0 &

> #Define the default CD Rom

> /bin/prefix -A /cd=//0/cd2.0

> nameloc &

> chkfsys /

> if test -f /etc/config/bin/tcpip.$NODE

> then

> /etc/config/bin/ph.$NODE

> else

> tinit -t/dev/con1 &

> tinit -T/dev/con2[2-6] &

> fi

If i take out the io-usb the keyboard works , else it freezes.

post121366: Re: QNX 4.25 2015 Experimental USB

2021-04-06T08:13:00Z

Here is my sysinit

#image: /boot/sys/boot -v

#image:/boot/sys/Proce32 -E0 -| 2

#image:/boot/sys/Slib32

#image:/boot/sys/Slib16

#image:/bin/Fsys -Hdisk160

#image:/bin/Fsys.ahci fsys -Ndsk1 -n0=hd1. -n5=cd1.

#image:/bin/mount -p /dev/hd1.0 /dev/hd1.0t77 /

#image:/bin/sinit TERM=qnxm

#export NODE=2

export KBD=en_CA_101.kbd

export ABLANG=en

export CON_KBD=USA

export TZ=est05edt04,M4.1.0/2,M10.5.0/2

/bin/rtc -| hw

Dev &

emu87 &

Pipe &

/bin/Dev.ser -N/dev/ser1 3f8,4 &

/bin/Dev.ser -N/dev/ser1 2f8,3 &

Dev.ansi -Q -n6 &

reopen /dev/con1

kbd $CON_KBD

prefix -A/dev/console=/dev/con1

Dev.pty &

Dev.pty -n16 &

io-usb

/bin/Fsys.umass fsys -Ndsk2 -n0=hd2. -n5=cd2.

Iso9660fsys /cd2.0=/dev/cd2.0 &

#Define the default CD Rom

/bin/prefix -A /cd=//0/cd2.0

nameloc &

chkfsys /

if test -f /etc/config/bin/tcpip.$NODE

then

/etc/config/bin/ph.$NODE

else

tinit -t/dev/con1 &

tinit -T/dev/con2[2-6] &

fi

post121365: Re: QNX 4.25 2015 Experimental USB

2021-04-06T06:29:30Z

I will try and let you know. Thanks for the replies.

post121323: Re: QNX 4.25 2015 Experimental USB

2021-03-10T12:14:28Z

Hi,

Maybe it is different in combination with Photon, but for our QNX Windows based system USB keyboard works in console mode as well. We start it using these commands:

io-usb

devu-kbd

Dev32.ansi -Q -n 6 -d/dev/usbkbd0

/Christian

post121295: Re: Seeking guidance on Socket crashing issues

2021-02-25T15:53:11Z

Yes I understand that. Unfortunately we cannot deploy the new TCPIP stack into our field kit as it sits a few thousand feet down on sea bed even though I suspect that is the only solution.

I was more after help to see if anyone may know of any bugs in Socket that could crash it or if there is a certain type of interaction that it does not like.

Thanks again

post121294: Re: Seeking guidance on Socket crashing issues

2021-02-25T15:50:03Z

Hi Paul,

We recommend to update to latest TCP/IP 5.10 package. It provides Tcpip daemon instead of Socket. Socket is obsolete and it can not be supported anymore.

Respectfully,

Oleg

> HI there

>

> In our system we are seeing issues with Socket crashing out randomly after

> anywhere between 4 to 11 days of running fine.  The process crashes out with

> Net not long after it.  On the system we have dumper running and when we have

> looked at the dumps even though we cannot tell what it is doing the 3 crashes

> we had dumps for all terminated on the same instruction.  I am hoping someone

> here might be able to aid diagnosing Socket.

>

> I have attached the snippet from wd utility that we get.  The issue is not

> deterministic.

>

> We have a PC connected to an Ampro CM420 board via  a 5 port switch.  We are

> running Modbus TCP comms, ping and occasional telnet sessions in to the board.

>   We also have a SNTP client running on the board requesting time updates

> every 60 seconds from the PC.

>

> We have this issue on field deployed kit also.  The setup we are running is

> just a boiled down setup to recreate the problem.

>

> Socket and sometimes Net also will crash.  The rest of our system stays up and

>  running fine until it fails to open connections etc then it is taken down by

> our supervisor process.

>

> I have attached screenshot of sin ver output to give versions.

>

> 1.  Are there any known issues with Socket?

> 2.  Any guidance based on the view of the dumper output.  (I appreciate it

> probably gets nothing)

>

> I can supply the dump file if needed

>

> Thanks for any help

>

> Paul

>

>

>

post121292: Seeking guidance on Socket crashing issues

2021-02-25T12:49:26Z

HI there

In our system we are seeing issues with Socket crashing out randomly after anywhere between 4 to 11 days of running fine.  The process crashes out with Net not long after it.  On the system we have dumper running and when we have looked at the dumps even though we cannot tell what it is doing the 3 crashes we had dumps for all terminated on the same instruction.  I am hoping someone here might be able to aid diagnosing Socket.

I have attached the snippet from wd utility that we get.  The issue is not deterministic.

We have a PC connected to an Ampro CM420 board via  a 5 port switch.  We are running Modbus TCP comms, ping and occasional telnet sessions in to the board.  We also have a SNTP client running on the board requesting time updates every 60 seconds from the PC.

We have this issue on field deployed kit also.  The setup we are running is just a boiled down setup to recreate the problem.

Socket and sometimes Net also will crash.  The rest of our system stays up and running fine until it fails to open connections etc then it is taken down by our supervisor process.

I have attached screenshot of sin ver output to give versions.

1.  Are there any known issues with Socket?

2.  Any guidance based on the view of the dumper output.  (I appreciate it probably gets nothing)

I can supply the dump file if needed

Thanks for any help

Paul

post121291: Re: QNX 4.25 2015 Experimental USB

2021-02-24T09:29:07Z

Hello Voicu,

Sorry for the delay with my answer. USB keyboard is not supported in console mode. You have to launch Photon to use USB keyboard. If you need console to work properly, then you can launch io-usb-ehci instead of io-usb to work with EHCI controllers (mostly mass storage devices).

Respectfully,

Oleg

> Hello , and thanks for the replies.

> USB Legacy its ENABLED in BIOS , and i activated the USB Stack from the

> Experimental CD (because i am installing from an USB DVD RW).

> If i take out the io-usb from sysinit the keyboard works fine.

> If i run the io-usb from command line, it recognizes the USB DVDRW, and after

> that the keyboard freeezes.

post121258: Re: QNX 4.25 2015 Experimental USB

2021-02-12T09:30:43Z

Hello , and thanks for the replies.

USB Legacy its ENABLED in BIOS , and i activated the USB Stack from the Experimental CD (because i am installing from an USB DVD RW).

If i take out the io-usb from sysinit the keyboard works fine.

If i run the io-usb from command line, it recognizes the USB DVDRW, and after that the keyboard freeezes.

post121257: Re: QNX 4.25 2015 Experimental USB

2021-02-12T09:02:41Z

Hello Voicu,

Have you enabled USB support in boot menu while installing from experimental CD? Or have you used USB legacy?

Respectfully,

Oleg

> Hello. I have a miniPC Jetway FHP792x , which has only USB ports. I manage to

> install the experimental product suite 2015, the usb keyboard works in the

> installer just fine. After that i manage to make the usb keyboard work with

> the " Input kbd -R fd -d / dev / usbkbd0" in sysinit. But if i want to start

> the io-usb the PC freezes.

> Is there a bypass or a fix for this?

> Thank you very much!

post121256: Re: QNX 4.25 2015 Experimental USB

2021-02-12T05:50:40Z

I think, it might cause by usb 3.0 stack.

You should enter BIOS > CPU config > South Bridge . And, disable USB 3.0 or XHCI. Then check again.

post121251: QNX 4.25 2015 Experimental USB

2021-02-10T09:07:00Z

Hello. I have a miniPC Jetway FHP792x , which has only USB ports. I manage to install the experimental product suite 2015, the usb keyboard works in the installer just fine. After that i manage to make the usb keyboard work with the " Input kbd -R fd -d / dev / usbkbd0" in sysinit. But if i want to start the io-usb the PC freezes.

Is there a bypass or a fix for this?

Thank you very much!

post121250: Re: USB driver issue

2021-02-09T09:53:13Z

Hi Christian,

We have not faced of this issue before. To debug it we should reproduce the issue with specified HW.

Respectfully,

Oleg

> Hi Oleg,

>

>   I have looked into the above issue again from our side after it had been

> observed again and I have a few findings that may be of interest:

>

> * It seems certain USB input devices are more likely to cause issues with the

> USB driver. For example, with a "Microsoft Intellimouse Optical USB Mouse" we

> can see that the 'usb' tool often reports input/output errors if executed

> while moving the mouse pointer. The same does not happen for other input

> devices, such as HP USB mouse or Kensington trackball.

>

> * It seems certain models of USB memory sticks are more likely than others to

> cause the entire USB driver to stop working as was mentioned in previous posts

> . For example, Sandisk Cruzer Blade drives appear to be more likely to cause

> these issues than other models. To provoke such issues, we have found that if

> you run the 'usb' command to check on USB device status while copying files to

>  the USB drive it can easily cause input/output error for these Sandisk

> devices. And in some cases, the USB driver never fully recovers.

>

> * As mentioned earlier, it is generally enough to slay and re-start io-usb

> (and then associated drivers like devu-mouse) to get everything up and running

>  again.

>

> Is there any additional information you can think of that we could try to

> collect to give you an even better picture of what's really going on?

post121249: Re: USB driver issue

2021-02-09T08:44:13Z

Hi Oleg,

I have looked into the above issue again from our side after it had been observed again and I have a few findings that may be of interest:

* It seems certain USB input devices are more likely to cause issues with the USB driver. For example, with a "Microsoft Intellimouse Optical USB Mouse" we can see that the 'usb' tool often reports input/output errors if executed while moving the mouse pointer. The same does not happen for other input devices, such as HP USB mouse or Kensington trackball.

* It seems certain models of USB memory sticks are more likely than others to cause the entire USB driver to stop working as was mentioned in previous posts. For example, Sandisk Cruzer Blade drives appear to be more likely to cause these issues than other models. To provoke such issues, we have found that if you run the 'usb' command to check on USB device status while copying files to the USB drive it can easily cause input/output error for these Sandisk devices. And in some cases, the USB driver never fully recovers.

* As mentioned earlier, it is generally enough to slay and re-start io-usb (and then associated drivers like devu-mouse) to get everything up and running again.

Is there any additional information you can think of that we could try to collect to give you an even better picture of what's really going on?

post121108: Shared LIbs Query

2020-11-19T12:44:13Z

Hi All

At the moment I am examining a possible solution to an issue we have.

For info we have a base system install of QNX 4 that launches and sets up Socket usually and is compiled and linked with its version of Socket3 lib.  We have another set of processes that are compiled and linked separately as effectively an application that is installed onto that base system.  The yare usually also compiled with the version of Socket3 lib appropriate to Socket.

However we have been issues with it crashing a lot.  As such we are looking to move to TCPIP 5.1 stack and noted its lib is slightly different.  As such the base system needs to run this and obviously be linked with the correct lib.

The problem we have is a nasty need to retain backwards compatibility with the application processes.   As such the compiled processes need to run on the system with Socket or TCPIP.

As such I was looking at perhaps compiling the two shared libs into a common lib that the processes are then linked with.  From the little I can find I understand QNX4 does not officially support shared libs and that it can be troublesome.

We are trying to avoid the need to maintain, compile, link and test the application and base system software twice as this presents a maintenance overhead that is too big.

So i wondered is it still possible to get mkshlib and its documentation from somewhere.  Also has anyone got any experience or advice they could share about such a option?

Thanks And regards

Paul

post121091: Re: USB driver issue

2020-11-12T05:24:45Z

Hi Darel,

Here is a couple of recommendations:

1) Try to play with USB options in BIOS (usually in Advanced-> USB Configuration).

2) There is two mouse devices —  /dev/mousein (created by Mouse manager) and /dev/usbmouse0 (usb-mouse). Try to use USB mouse with Input manager. Change the line in your /etc/config/trap/input.$NODE for mouse to:

Input msoft fd -d/dev/usbmouse0

Make backup of input.$NODE before and don't forget for keyboard.

Respectfully,

Oleg

> Hi,

>   We have not managed to find a way to reliably reproduce the issue, but it

> did happens once again and we could collect the information you requested. See

>  attached zip file for various sin outputs.

>   Slaying and restarting io-usb (and other drivers that depend in it, like

> devu-mouse) resolved the issue so it seems that io-usb ends up in some state

> that it cannot recover from but that a restart resolves.

post121078: Re: Net.r6040 network driver

2020-11-08T08:31:07Z

Пришлось самостоятельно исправлять ошибки в сетевом драйвере, он просто не загружал свой MAC из EEPROM.

post121064: Re: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

2020-11-05T00:31:39Z

Most companies argue which version is the best one but it depends on the company you work for. I work in Los Angeles It Services https://www.generationix.com/los-angeles-managed-it-services/ and we work with SMB version 1 and it is a really nice version as it is very stable and has fewer bugs than other versions do. So it is a really personal thing which version to use as a lot of companies use different versions because of personal reasons. I hope one day we will have one stable version for all IT companies and there will be no need to learn every version. As for now, I will use the same version as my company uses.

post121063: Re: USB driver issue

2020-11-04T22:12:03Z

Hi,

We have not managed to find a way to reliably reproduce the issue, but it did happens once again and we could collect the information you requested. See attached zip file for various sin outputs.

Slaying and restarting io-usb (and other drivers that depend in it, like devu-mouse) resolved the issue so it seems that io-usb ends up in some state that it cannot recover from but that a restart resolves.

post121031: Re: USB driver issue

2020-10-12T10:29:17Z

Hi Darel,

It's too difficult to debug it remotely. But if this issue will occur again then you can send me output of following commands just after the system start:

sin

sin ar

sin ver

sin ir

show_pci -vvv

And output of sin ar just after the issue occurs.

Please send the output in one tarball.

Respectfully,

Oleg

> Hi,

>

> We have not been able to provoke the error but during the weekend it

> happened again. No-one was using the system at the time, it was just up and

> running with communication on serial and network ports to associated equipment

> .

> When running command "usb" I get the following output:

> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD

> device 1 - descriptors - Input/output error

> device 2 - descriptors - Input/output error

> device 3 - descriptors - Input/output error

> device 4 - descriptors - Input/output error

>

>

post121030: Re: USB driver issue

2020-10-12T09:02:33Z

Hi,

We have not been able to provoke the error but during the weekend it happened again. No-one was using the system at the time, it was just up and running with communication on serial and network ports to associated equipment.

When running command "usb" I get the following output:

USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD

device 1 - descriptors - Input/output error

device 2 - descriptors - Input/output error

device 3 - descriptors - Input/output error

device 4 - descriptors - Input/output error

post120990: Re: Proc32 Updates

2020-10-01T11:13:38Z

HI Oleg

Thanks for the information. Yeah ours fails usually couple of days into execution so not this.

Thanks again

Paul

post120989: Re: Proc32 Updates

2020-10-01T10:58:21Z

Hi Paul,

The readme says about -E0 option of Proc32 only. This is workaround for internal QNX kernel PCI handler (alternate code for BIOS PCI functions calls). The issue with PCI handler occurs at the very beginning of OS booting (i.g., when Fsys.* driver starts). So the QNX can't launch at all. If you can launch QNX on Ampro CM420 without -E0 then you do not have this PCI issue. -E0 option doesn't affect any other aspects of memory usage.

Respectfully,

Oleg

> The readme file for 4.25R is not very clear. it just states modern boards.

> Currently we use Ampro CM420 boards from around 2005 with CompactFlash storage

> .

post120988: Re: Proc32 Updates

2020-10-01T10:20:43Z

The readme file for 4.25R is not very clear. it just states modern boards. Currently we use Ampro CM420 boards from around 2005 with CompactFlash storage.

post120987: Re: Proc32 Updates

2020-10-01T10:19:34Z

Currently we use 4.25Q and the version in the foundry27 archives with regard to the -E0 issue is 4.25R

post120976: Re: Proc32 Updates

2020-09-30T19:24:32Z

Hi Paul,

What Proc32 version do you ask about? What version of Proc32 do you use?

Respectfully,

Oleg

> Hi All

>

> Recently I am investigating some issues on our system with QNX where processes

> randomly crash supposedly with SIGSEGV issues.

>

> I have been looking around and came across an update to Proc32 on this site.

> The description in its read me states that the change is in place to work

> around 386 memory protections issues on more modern boards.

>

> I am wondering if anyone could shed some more light on this change as to how

> issues manifested etc.

>

> Thanks

>

> Paul

post120974: Proc32 Updates

2020-09-30T16:04:48Z

Hi All

Recently I am investigating some issues on our system with QNX where processes randomly crash supposedly with SIGSEGV issues.

I have been looking around and came across an update to Proc32 on this site. The description in its read me states that the change is in place to work around 386 memory protections issues on more modern boards.

I am wondering if anyone could shed some more light on this change as to how issues manifested etc.

Thanks

Paul

post120961: Re: USB driver issue

2020-09-29T08:19:16Z

Hi Darel,

Sorry for the delay with my answer. We have not faced off such issue before. Is it reproducible behavior?

Respectfully,

Oleg

> I ran into a strange issue with the USB driver last week on a new computer

> model being tested for use with our QNX 4.25 application.

> The USB mouse pointer suddeny started being hardly responsive - it moved in

> large steps with a few seconds interval when moving the mouse.

> When running the "usb" command on the command line, it was also slow to

> respond and showed error messages about "input/output error" for all USB

> devices on the bus.

>

> We use the USB 2.00L drivers and the Proc32 4.25R kernel.

> A reboot resolve the problem.

>

> Have you seen this problem before? Is there anyway for me to find more

> information about possible root cause in case it happens again?

post120943: USB driver issue

2020-09-21T06:30:58Z

I ran into a strange issue with the USB driver last week on a new computer model being tested for use with our QNX 4.25 application.

The USB mouse pointer suddeny started being hardly responsive - it moved in large steps with a few seconds interval when moving the mouse.

When running the "usb" command on the command line, it was also slow to respond and showed error messages about "input/output error" for all USB devices on the bus.

We use the USB 2.00L drivers and the Proc32 4.25R kernel.

A reboot resolve the problem.

Have you seen this problem before? Is there anyway for me to find more information about possible root cause in case it happens again?

post120919: Re: IRQ Issues

2020-08-31T20:56:56Z

Hi Steve,

It seems that your hardware is quite modern and its main working mode is UEFI/APIC. But QNX 4.25 does not support APIC. Many modern hardware configurations have legacy mode fallback, but most of them are bad-configured and use the same IRQ for most devices.

There is no siple solution if it's available at all. You can try to play with BIOS settings. Or try to use another BIOS firmware (may be old one). But it’s on your own responsibility.

Respectfully,

Oleg

> When I do a show_pci. Display, Mass Storage and Network card #1 show

> Interrupt line 11. Only Network card #2 show interrupt line 10. Is there

> something I can do to solve this issue ? Network card #1 shows 1000mb in

> netinfo but is extremely slow.

post120918: IRQ Issues

2020-08-31T20:26:52Z

When I do a show_pci. Display, Mass Storage and Network card #1 show Interrupt line 11. Only Network card #2 show interrupt line 10. Is there something I can do to solve this issue ? Network card #1 shows 1000mb in netinfo but is extremely slow.

post120874: Re: Utopia font

2020-07-29T01:45:13Z

Hi Oleg,

Thank you very much for the font.

Yes I would appreciate it if you could post the tools for converting ttf to phf.

Regards,

Pete

Get Outlook for iOS<https://urldefense.proofpoint.com/v2/url?u=https-3A__aka.ms_o0ukef&d=DwIF-g&c=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE&r=0BZBymgZ1Q5cDybFJfjfeqcwXILO6Uigbb8DkqX94ME&m=dzGG3HBdjkfa5Es6HS8ovAhQi_4d_K3EPf2qBmmmNOY&s=j9qUJHHO_fZ7HwZo5Apngc_tUrtrRpMJjupgski1VI4&e= >

________________________________

From: Oleg Bolshakov <community-noreply@qnx.com>

Sent: Monday, July 27, 2020 9:48:01 PM

To: general-qnx4 <general-qnx4@community.qnx.com>

Subject: Re: Utopia font

Hello Pete,

Please find attached the Utopia 80b font.

Also I can post here tools for converting TTF to PHF fonts. But as is, no warranty.

Respectfully,

Oleg

> Hello,

>

> The Utopia font in QNX 4.25 seems to go up to a maximum of 64pt bold but we

> now have a requirement for a font size of 80b. Is this possible?

>

> It is required on a phindows session and not on the QNX console.

>

> I realise that the phindows of this vintage can only recognise .phf fonts.

>

> Does utop80b.phf exist? If it doesn’t can it be created somehow?

>

> Thanks,

> Pete

_______________________________________________

General

http://community.qnx.com/sf/go/post120869

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120873: Re: Utopia font

2020-07-29T01:45:00Z

Thank you very much, Mr Oleg,

Let me try it and report result :).

post120872: Re: Utopia font

2020-07-28T20:43:12Z

Hello Cong,

Attaching ttf2dbf util and readme. As is, no warranty.

Respectfully,

Oleg

> Hello Oleg,

>

> Please attach this "converting TTF to PHF fonts" tool, I need convert some

> font myself.

> I need some fonts for display Vietnamese. Hic

>

> >

> > Also I can post here tools for converting TTF to PHF fonts. But as is, no

> > warranty.

> >

> > Respectfully,

> > Oleg

> >

> >

post120870: Re: Utopia font

2020-07-28T04:13:34Z

Hello Oleg,

Please attach this "converting TTF to PHF fonts" tool, I need convert some font myself.

I need some fonts for display Vietnamese. Hic

>

> Also I can post here tools for converting TTF to PHF fonts. But as is, no

> warranty.

>

> Respectfully,

> Oleg

>

>

post120869: Re: Utopia font

2020-07-27T20:48:00Z

Hello Pete,

Please find attached the Utopia 80b font.

Also I can post here tools for converting TTF to PHF fonts. But as is, no warranty.

Respectfully,

Oleg

> Hello,

>

> The Utopia font in QNX 4.25 seems to go up to a maximum of 64pt bold but we

> now have a requirement for a font size of 80b. Is this possible?

>

> It is required on a phindows session and not on the QNX console.

>

> I realise that the phindows of this vintage can only recognise .phf fonts.

>

> Does utop80b.phf exist? If it doesn’t can it be created somehow?

>

> Thanks,

> Pete

post120861: Utopia font

2020-07-23T12:42:51Z

Hello,

The Utopia font in QNX 4.25 seems to go up to a maximum of 64pt bold but we now have a requirement for a font size of 80b. Is this possible?

It is required on a phindows session and not on the QNX console.

I realise that the phindows of this vintage can only recognise .phf fonts.

Does utop80b.phf exist? If it doesn’t can it be created somehow?

Thanks,

Pete

post120844: Re: Siemens IPC347E Graphics driver

2020-07-17T10:31:19Z

Hello Pet,

This problem may occur due to incorrect installation of the video driver. Try to find and delete the latest driver version that you installed and restart your computer after that. Download any windows 10 registry cleaner (here is the list of the best cleaners https://thinkmobiles.com/blog/best-registry-cleaner-tools/) and clean your registry. Then download the program for automatic driver updates and it will do all the work for you and select the right driver for your computer. After installing all the drivers, restart your computer again and this problem should disappear.

Good luck, sincerely Mark.

post120710: Re: Net.e1000 & i350

2020-05-29T23:17:00Z

Hugh and Oleg,

Thanks for the assistance. Using "sin ar" helped me identify a different initialization script that was being used. After modifying the correct rc script, the network config at boot time is successful and driver functions as expected.

Will let you know if i have any other issues.

Much appreciated.

post120702: Re: Net.e1000 & i350

2020-05-29T12:25:29Z

Hi Alex,

In case if Hugh's conclusion isn't help. Please attach here output of following commands:

sin ver

sin ar

From which QNX 4 installation CD have you installed your system? What Net.e1000 driver do you use?

Respectfully,

Oleg

> Are you running Net? You have to run Net before starting any drivers.

>

> Hugh.

>

> On 2020-05-28, 6:02 PM, "Alex Lam" <community-noreply@qnx.com> wrote:

>

>     Hi,

>

>     I'm new to QNX and have been having some issues with the Net.e1000 driver

> and an Intel I350T2V2 device. Device ID 1521h

>

>     #Net.e1000 -I0 -l3 &

>

>     Net.e1000: INITIALIZATION ERROR 4

>     net_reg failed

>

>     Any help would be appreciated.

>     Thanks,

>     Alex

>

>

>

>     _______________________________________________

>

>     General

>     http://community.qnx.com/sf/go/post120700

>     To cancel your subscription to this discussion, please e-mail general-qnx4

> -unsubscribe@community.qnx.com

>

post120701: Re: Net.e1000 & i350

2020-05-29T12:01:35Z

Are you running Net? You have to run Net before starting any drivers.

Hugh.

On 2020-05-28, 6:02 PM, "Alex Lam" <community-noreply@qnx.com> wrote:

    Hi,

    I'm new to QNX and have been having some issues with the Net.e1000 driver and an Intel I350T2V2 device. Device ID 1521h

    #Net.e1000 -I0 -l3 &

    Net.e1000: INITIALIZATION ERROR 4

    net_reg failed

    Any help would be appreciated.

    Thanks,

    Alex

    _______________________________________________

    General

    http://community.qnx.com/sf/go/post120700

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120700: Net.e1000 & i350

2020-05-28T22:02:00Z

Hi,

I'm new to QNX and have been having some issues with the Net.e1000 driver and an Intel I350T2V2 device. Device ID 1521h

#Net.e1000 -I0 -l3 &

Net.e1000: INITIALIZATION ERROR 4

net_reg failed

Any help would be appreciated.

Thanks,

Alex

post120109: Re: RE: Net.e1000 Source

2019-12-12T17:24:20Z

Hi Martin,

Thank you for doing things so clear.

Respectfully,

Oleg

> Hi Paul,

>

> Just to fill you in here...

> BTW... I'm Martin from QNX, I've been managing QNX4 stuff forever an try to

> help resolve the problems that still come in occasionally.

>

> Hugh is on vacation until the New Year.

> Oleg, is the main resource responsible for QNX 4 support via forums.

>

> In your last message you stated that 'this is looking like a interrupt

> problem'...

> I have asked Oleg to work with you to help determine if this is an interrupt

> problem, or a network driver problem.  We have seem may issues related to

> interrupt sharing. Hopefully Oleg will be able to help you resolve if it's

> interrupts related.

> If not and interrupts are ruled out, then we need to work on getting your

> hardware here, and booking Hugh's time, under a CSP agreement to debug the

> ethernet driver.

>

> -Martin.

>

>

>

>

>

> -----Original Message-----

> From: Oleg Bolshakov <community-noreply@qnx.com>

> Sent: Thursday, December 12, 2019 3:38 AM

> To: general-qnx4 <general-qnx4@community.qnx.com>

> Subject: Re: Net.e1000 Source

>

> Hi Paul,

>

> Is it HW specific issue? Or can you describe the steps to reproduce the issue

> under different HW configurations?

>

> Respectfully,

> Oleg

>

> > HI All

> >

> > I wondered is the person who was maintaining the Net.e1000 driver still

> about.

> >   I posted earlier in the year that I was suffering lock ups when

> > Ethernet traffic just stopping on the board I use.

> >

> > We initially thought we had found way by locking the driver at  10

> > Megabit Full Duplex.  However that seems to have failed.

> >

> > We are wanting to run detailed investigations of our own and are

> > looking to try obtain the source or speak to the person who created/

> maintained it.

> >

> > It is probably along shot.

> >

> > Thanks in advance

> >

> > Paul

>

>

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post120106

> To cancel your subscription to this discussion, please e-mail general-qnx4-

> unsubscribe@community.qnx.com

post120107: RE: Net.e1000 Source

2019-12-12T16:40:36Z

Hi Paul,

Just to fill you in here...

BTW... I'm Martin from QNX, I've been managing QNX4 stuff forever an try to help resolve the problems that still come in occasionally.

Hugh is on vacation until the New Year.

Oleg, is the main resource responsible for QNX 4 support via forums.

In your last message you stated that 'this is looking like a interrupt problem'...

I have asked Oleg to work with you to help determine if this is an interrupt problem, or a network driver problem.  We have seem may issues related to interrupt sharing. Hopefully Oleg will be able to help you resolve if it's interrupts related.

If not and interrupts are ruled out, then we need to work on getting your hardware here, and booking Hugh's time, under a CSP agreement to debug the ethernet driver.

-Martin.

-----Original Message-----

From: Oleg Bolshakov <community-noreply@qnx.com>

Sent: Thursday, December 12, 2019 3:38 AM

To: general-qnx4 <general-qnx4@community.qnx.com>

Subject: Re: Net.e1000 Source

Hi Paul,

Is it HW specific issue? Or can you describe the steps to reproduce the issue under different HW configurations?

Respectfully,

Oleg

> HI All

>

> I wondered is the person who was maintaining the Net.e1000 driver still about.

>   I posted earlier in the year that I was suffering lock ups when

> Ethernet traffic just stopping on the board I use.

>

> We initially thought we had found way by locking the driver at  10

> Megabit Full Duplex.  However that seems to have failed.

>

> We are wanting to run detailed investigations of our own and are

> looking to try obtain the source or speak to the person who created/maintained it.

>

> It is probably along shot.

>

> Thanks in advance

>

> Paul

_______________________________________________

General

http://community.qnx.com/sf/go/post120106

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120106: Re: Net.e1000 Source

2019-12-12T08:37:53Z

Hi Paul,

Is it HW specific issue? Or can you describe the steps to reproduce the issue under different HW configurations?

Respectfully,

Oleg

> HI All

>

> I wondered is the person who was maintaining the Net.e1000 driver still about.

>   I posted earlier in the year that I was suffering lock ups when Ethernet

> traffic just stopping on the board I use.

>

> We initially thought we had found way by locking the driver at  10 Megabit

> Full Duplex.  However that seems to have failed.

>

> We are wanting to run detailed investigations of our own and are looking to

> try obtain the source or speak to the person who created/maintained it.

>

> It is probably along shot.

>

> Thanks in advance

>

> Paul

post120096: Re: Net.e1000 Source

2019-12-03T13:53:28Z

You would need to speak to your local QNX sales rep and organize with him to engage our services to take a look at your problem. We would also need to have your hardware.

Hugh.

On 2019-12-03, 8:50 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Ah ok.



    I presume there would be no way to engage your services in that case as I presume the driver was developed for a product the company you work for uses QNX 4 on?



    We are still having issues with loss of comms out of Intel i210 interface using the driver.  It seems to be IRQ related but its at point now where debug is only possible  with source.



    If it is not possible to engage your services thank you for the help you have provided.







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post120095

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120095: Re: Net.e1000 Source

2019-12-03T13:50:47Z

Ah ok.

I presume there would be no way to engage your services in that case as I presume the driver was developed for a product the company you work for uses QNX 4 on?

We are still having issues with loss of comms out of Intel i210 interface using the driver. It seems to be IRQ related but its at point now where debug is only possible with source.

If it is not possible to engage your services thank you for the help you have provided.

post120094: Re: Net.e1000 Source

2019-12-03T13:45:11Z

Hi Paul,

The reason that we don't distribute QNX4 source code is that there are proprietary header and library files required to compile the network drivers, so even if we sent you the source to the driver, you wouldn't be able to compile it.

Hugh.

On 2019-12-03, 8:28 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    HI Hugh



    Do you have a contact email address I could email you at to discuss the driver source.  I know you said you do not hand out QNX4 source.  I would like to discuss if there is anyway to procure it or if there is a path available to go through to obtain it.



    Thank you kindly in advance



    Paul











    _______________________________________________



    General

    http://community.qnx.com/sf/go/post120093

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120093: Re: Net.e1000 Source

2019-12-03T13:29:09Z

HI Hugh

Do you have a contact email address I could email you at to discuss the driver source. I know you said you do not hand out QNX4 source. I would like to discuss if there is anyway to procure it or if there is a path available to go through to obtain it.

Thank you kindly in advance

Paul

post120092: Re: Net.e1000 Source

2019-11-29T13:34:17Z

The last change to the driver was in 2016 to support the i219 chipset.

On 2019-11-29, 4:00 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Ah that is unfortunate to hear.  Thankyou for the driver though.  When does this one date from?



    Also is there any kind of change history for the various versions of the driver anywhere?



    Thanks



    Paul







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post120090

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120090: Re: Net.e1000 Source

2019-11-29T09:00:57Z

Ah that is unfortunate to hear. Thankyou for the driver though. When does this one date from?

Also is there any kind of change history for the various versions of the driver anywhere?

Thanks

Paul

post120088: Re: Net.e1000 Source

2019-11-28T19:19:07Z

We don't supply QNX4 source code, but I have attached the latest version of the Net.e1000 driver for you to try.

On 2019-11-28, 7:20 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    HI All



    I wondered is the person who was maintaining the Net.e1000 driver still about.  I posted earlier in the year that I was suffering lock ups when Ethernet traffic just stopping on the board I use.



    We initially thought we had found way by locking the driver at  10 Megabit Full Duplex.  However that seems to have failed.



    We are wanting to run detailed investigations of our own and are looking to try obtain the source or speak to the person who created/maintained it.



    It is probably along shot.



    Thanks in advance



    Paul







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post120087

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post120087: Net.e1000 Source

2019-11-28T12:21:13Z

HI All

I wondered is the person who was maintaining the Net.e1000 driver still about. I posted earlier in the year that I was suffering lock ups when Ethernet traffic just stopping on the board I use.

We initially thought we had found way by locking the driver at 10 Megabit Full Duplex. However that seems to have failed.

We are wanting to run detailed investigations of our own and are looking to try obtain the source or speak to the person who created/maintained it.

It is probably along shot.

Thanks in advance

Paul

post120078: Re: Net.r6040 network driver

2019-11-06T17:05:47Z

Приветствую!

А ваш драйвер умеет вычитывать MAC-адрес из EEPROM этой сетевой карты? А то вот нам не повезло, и мы получили драйвер для RDC R6040 (входящий в состав PC/104-платы Vortex86DX) не только не умеющий это делать, но даже не умеющий устанавливать MAC-адрес по опции драйвера (типа, так: "io-pkt-v4 -d vortex mac=010203040506") из-за ошибки в коде (это мы поправили) и всегда использующий 00:00:60:00:00:01. Могли бы вы прислать ваш драйвер с исходниками для QNX 6.5?

C Уважением, Николай Распопов.

raspopov@cherubicsoft.com

post120038: Re: Dev.con/ditto issue

2019-10-14T16:45:08Z

Hi Oleg,

I had a feeling you were going to say that. I'll try a workaround then.

Thanks for your time,

Robert

post120035: Re: Dev.con/ditto issue

2019-10-14T12:36:11Z

Hi Robert,

I guess that this is HW/BIOS specific issue. Many HW features are emulated in BIOS on modern boards.

Respectfully,

Oleg

> Hi Oleg,

>

> Checking in with you to let you know that I sourced some additional

> hardware and the problem occurs with the Intel Atom D2550 CPU too.

>

> Thanks,

>

> Robert

post120034: Re: QNX4.25 mem/pmem.c(188)

2019-10-14T12:35:14Z

Hi Leonid,

Is it HW issue or it repeats on several different HW? In first case your HW is required to debug the issue.

Respectfully,

Oleg

> On one of the controllers with QNX4.25 we get an irregular OS crash (attached

> photo).

>

> ...

> "mem / pmem.c (188) inserting [fffff, 1] between [3271, d] and [fffff, 1]"

> ...

>

> The only thing that was found was the too mach old time discussion https://www

> .openqnx.com/newsgroups/viewtopic.php?t=3390,

> but it didn’t clarify anything.

>

> The controller uses an industrial PCI-6028 board, MOXA multiport boards (4 pcs

> ., 8 ports each),

> updated driver Dev32.ser .

>

> Have you come across a similar emergency conclusion? What could be the reason?

post120027: QNX4.25 mem/pmem.c(188)

2019-10-10T11:36:00Z

On one of the controllers with QNX4.25 we get an irregular OS crash (attached photo).

...

"mem / pmem.c (188) inserting [fffff, 1] between [3271, d] and [fffff, 1]"

...

The only thing that was found was the too mach old time discussion https://www.openqnx.com/newsgroups/viewtopic.php?t=3390,

but it didn’t clarify anything.

The controller uses an industrial PCI-6028 board, MOXA multiport boards (4 pcs., 8 ports each),

updated driver Dev32.ser .

Have you come across a similar emergency conclusion? What could be the reason?

post120025: Re: Dev.con/ditto issue

2019-10-08T18:36:29Z

Hi Oleg,

Checking in with you to let you know that I sourced some additional hardware and the problem occurs with the Intel Atom D2550 CPU too.

Thanks,

Robert

post119927: Re: how to read the actual photon region

2019-09-13T07:14:49Z

Hi Oleg,

thank you for your valuable suggestions.

These options have also come to my mind.

Best regards,

Sebastian

> Hi Sebastian,

>

> Unfortunately, PgReadScreen() is not implemented in QNX 4. So you have two

> option:

>

> 1. Use snapshot utility.

> 2. In case of using Pg.flat* driver you can determine physical framebuffer

> address, map it in your app and read from it according to current graphics

> mode.

>

> Respectfully,

> Oleg

>

post119917: Re: how to read the actual photon region

2019-09-12T14:24:55Z

Hi Sebastian,

Unfortunately, PgReadScreen() is not implemented in QNX 4. So you have two option:

1. Use snapshot utility.

2. In case of using Pg.flat* driver you can determine physical framebuffer address, map it in your app and read from it according to current graphics mode.

Respectfully,

Oleg

> We need to know the best way to read in a photon region to an image or char

> array. So we have access to the pixel color data. We are using QNX4.25.

> We want to grab the screen from a process, which will not draw to photon and

> should just read back what another process have drawn.

>

> We did not find a suitable function to accomplish that, we just found out that

> QNX6 has the PgReadScreen function to do this.

post119903: how to read the actual photon region

2019-09-11T05:00:06Z

We need to know the best way to read in a photon region to an image or char array. So we have access to the pixel color data. We are using QNX4.25.

We want to grab the screen from a process, which will not draw to photon and should just read back what another process have drawn.

We did not find a suitable function to accomplish that, we just found out that QNX6 has the PgReadScreen function to do this.

post119876: Re: Dev.con/ditto issue

2019-09-04T19:16:16Z

Hi Robert,

We have reproduced the issue too. We need to debug this. I'll let you know about results.

Respectfully,

Oleg

> Hi Oleg,

>

> Just reporting back that a fresh install off of the 2015 Boot CD didn't

> change anything. I tried both the 16 and 32 bit versions of Dev/Dev.con too.

>

> Thanks,

>

> Robert

post119857: Re: Dev.con/ditto issue

2019-09-03T21:56:45Z

Hi Oleg,

Just reporting back that a fresh install off of the 2015 Boot CD didn't change anything. I tried both the 16 and 32 bit versions of Dev/Dev.con too.

Thanks,

Robert

post119844: Re: Dev.con/ditto issue

2019-08-29T17:17:48Z

Hi Oleg,

I can try a fresh install from the 2015 Boot CD but in the meantime I have the setup down to a minimum to reproduce the problem. Attached are pictures of the kernel build file, sysinit and my "sin ver" output so you can compare program versions.

To reproduce, let the node boot up and log into console #1. Press CTRL-ALT-4 (console #4) and press Enter to get a login prompt. Press CTRL-ALT-1 to get back to console #1 and run:

ditto -qk /dev/con4

Then do the steps I mentioned in the post above with those pictures (1-3) that were attached showing the issue.

Thanks,

Robert

post119842: Re: Dev.con/ditto issue

2019-08-29T12:13:06Z

Hi Robert,

We have not faced off such issue ever. I’ve noticed that you use QNX 4.24. Please check that issue exists with fresh install of current QNX 4.25.

We have 0x0f31 controller on hands, so we can try to reproduce the issue. Can you send me the sequence of actions to reproduce it?

Respectfully,

Oleg

> This scenario works just fine on other hardware and attached are three

> pictures.  The first shows me logging into a different console via a ditto

> session.  I typed a continuous stream of capital Xs but as you can see some

> get dropped in a very specific pattern.  The second picture is after I press

> Enter.  The third picture is after I typed the CTRL-e u keystroke to repaint

> the screen.

post119836: Re: Dev.con/ditto issue

2019-08-27T16:31:20Z

This scenario works just fine on other hardware and attached are three pictures. The first shows me logging into a different console via a ditto session. I typed a continuous stream of capital Xs but as you can see some get dropped in a very specific pattern. The second picture is after I press Enter. The third picture is after I typed the CTRL-e u keystroke to repaint the screen.

post119833: Re: Dev.con/ditto issue

2019-08-27T12:48:04Z

Hi Robert,

Does your scenario works fine on other hardware? Can you post screenshots/photos or video of the issue?

Respectfully,

Oleg

> I have an issue that when I ditto another console on the same system

> characters are dropped when typed.  Yet each console in and of itself draws

> perfectly fine when viewed/used outside of a ditto session.  If I use the CTRL

> -e u keystroke to repaint the screen while in a ditto session it updates just

> fine though but doing this even time after typing a few keystrokes gets a

> little old.  The system has an Intel J1900 1.99GHz CPU with the Vendor ID:

> 8086 and Device ID: f31h Display (VGA) integrated graphics.  I suspect this is

>  some sort of a VGA issue as this system cannot be run under gr.vga (vertical

> black lines in the GUI display) and only runs under gr.phi (with Hydra.ms and

> Pg.flatdc).  Any ideas as to what may be causing this?

post119832: Dev.con/ditto issue

2019-08-26T22:21:58Z

I have an issue that when I ditto another console on the same system characters are dropped when typed. Yet each console in and of itself draws perfectly fine when viewed/used outside of a ditto session. If I use the CTRL-e u keystroke to repaint the screen while in a ditto session it updates just fine though but doing this even time after typing a few keystrokes gets a little old. The system has an Intel J1900 1.99GHz CPU with the Vendor ID: 8086 and Device ID: f31h Display (VGA) integrated graphics. I suspect this is some sort of a VGA issue as this system cannot be run under gr.vga (vertical black lines in the GUI display) and only runs under gr.phi (with Hydra.ms and Pg.flatdc). Any ideas as to what may be causing this?

post119776: Buid error

2019-07-05T05:12:49Z

I am using QNX 4.6. I imported existing project which was already build on another machine. When i build the project on my machine it gives error below:

C:\QNX641\host\win32\x86\usr\bin\ntoarm-ld: cannot find -lMessage

cc: C:/QNX641/host/win32/x86/usr/bin/ntoarm-ld caught signal 1

make[7]: *** [C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter/Communication/MODBUS/Slave/arm/o-le/MODBUSSlave] Error 1

make[7]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter/Communication/MODBUS/Slave/arm/o-le'

make[6]: *** [install] Error 2

make[6]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter/Communication/MODBUS/Slave/arm'

make[5]: *** [install] Error 2

make[5]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter/Communication/MODBUS/Slave'

make[4]: *** [install] Error 2

make[4]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter/Communication/MODBUS'

make[3]: *** [install] Error 2

make[3]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter/Communication'

make[2]: *** [install] Error 2

make[2]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src/Transmitter'

make[1]: *** [install] Error 2

make[1]: Leaving directory `C:/Users/212553216/Documents/XMT1000/Nag_CLampOn_Dev/src'

make: *** [install] Error 2

post119523: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-15T15:20:30Z

At this point I think that your best bet would be to contact your QNX sales representative and make arrangements to send us your hardware, as we are unable to reproduce this problem with the hardware that we have.

Thanks, Hugh.

On 2019-02-15, 10:07 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Yeah I left a test running while off with PC at 10 Mbps FDX through a 100 Mbpos switch with board runnig at 100 Mbps FDX.



    It got to 27900 completions before it locked up







    > I left your test running last night, and this morning it is still running with

    >  1300 loops completed. This is running through a 100Mb/s switch.

    >

    >

    > On 2019-02-06, 4:19 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    >

    >     Latest status.

    >

    >     Ran with new board and it gets to 400 before locking up.

    >

    >     Setting PC to 10 Mbps FDX through switch with board set to 100 Mbps FDX.

    > Test appears to run without issue.  Have run sin proxies and sin timers and

    > there does not appear to be a build up of either.

    >

    >

    >

    >     _______________________________________________

    >

    >     General

    >     http://community.qnx.com/sf/go/post119487

    >     To cancel your subscription to this discussion, please e-mail general-qnx4

    > -unsubscribe@community.qnx.com

    >

    >













    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119522

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119522: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-15T15:07:47Z

Yeah I left a test running while off with PC at 10 Mbps FDX through a 100 Mbpos switch with board runnig at 100 Mbps FDX.

It got to 27900 completions before it locked up

> I left your test running last night, and this morning it is still running with

>  1300 loops completed. This is running through a 100Mb/s switch.

>

>

> On 2019-02-06, 4:19 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

>

>     Latest status.

>

>     Ran with new board and it gets to 400 before locking up.

>

>     Setting PC to 10 Mbps FDX through switch with board set to 100 Mbps FDX.

> Test appears to run without issue.  Have run sin proxies and sin timers and

> there does not appear to be a build up of either.

>

>

>

>     _______________________________________________

>

>     General

>     http://community.qnx.com/sf/go/post119487

>     To cancel your subscription to this discussion, please e-mail general-qnx4

> -unsubscribe@community.qnx.com

>

>

post119521: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-15T14:09:27Z

Hi

Sorry for the delay.

Here is a screen shot of the sin irq stuff. Doesn't mean much to me I am afraid

post119505: Re: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

2019-02-12T23:24:27Z

With regard to SMBfsys and smb versions we eed to move on from SMB v1.

I believe the source code for SMBfsys should be available as per the following:

You could ask QNX in the QNX4 Forum on Foundry27.

SMBfsys is essentially just the client side of Samba 2.2.12 (in QNX 6+ this is fsys-cifs) with a QNX manager wrapper around it. Given that Samba uses an open source license, QNX technically should be making the code available to you under that license.

For QNX 7, I built the base Samba source for client and server side and it was trivial.

post119490: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-07T10:29:17Z

Yeah will do. I'll be back at it today so will recreate the failure and get that info

post119489: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-06T13:14:30Z

Can you post the output from "sin" and "sin irq" when the lockup occurs?

On 2019-02-06, 4:19 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Latest status.



    Ran with new board and it gets to 400 before locking up.



    Setting PC to 10 Mbps FDX through switch with board set to 100 Mbps FDX.  Test appears to run without issue.  Have run sin proxies and sin timers and there does not appear to be a build up of either.







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119487

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119488: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-06T12:32:45Z

I left your test running last night, and this morning it is still running with 1300 loops completed. This is running through a 100Mb/s switch.

On 2019-02-06, 4:19 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Latest status.



    Ran with new board and it gets to 400 before locking up.



    Setting PC to 10 Mbps FDX through switch with board set to 100 Mbps FDX.  Test appears to run without issue.  Have run sin proxies and sin timers and there does not appear to be a build up of either.







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119487

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119487: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-06T09:18:58Z

Latest status.

Ran with new board and it gets to 400 before locking up.

Setting PC to 10 Mbps FDX through switch with board set to 100 Mbps FDX. Test appears to run without issue. Have run sin proxies and sin timers and there does not appear to be a build up of either.

post119486: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T16:36:52Z

I have run your script from my Ubuntu Linux PC to my QNX4 PC at 1Gb/s for 100 loops without any problems. The file size is 195MB.

I am now running the same test via a 100Mb/s switch to see if anything changes.

On 2019-02-05, 11:28 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    The memory stays consistent.



    We have over 2 Gig of Ram on board.  And still have 1600 Meg available.



    Virtual memory is at 1225/2000 odd Meg



    HeapL is 22798



    Nothing changes much.







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119485

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119485: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T16:28:22Z

The memory stays consistent.

We have over 2 Gig of Ram on board. And still have 1600 Meg available.

Virtual memory is at 1225/2000 odd Meg

HeapL is 22798

Nothing changes much.

post119484: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:48:18Z

Hmm nope

I have python 2.7.15 installed on windows 7. And do not set anything else except tick box in installer to run add to system PATH so I can run from command prompt.

Then from command line run: python ftp.py

Python fails immediately if it cannot do something as its runtime interpreted.

post119483: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:46:09Z

The Memory in the top section remains at about 1615/2031 M virtual sits at about  1219/2088 M

But I am running test again with switch back in and PC forced to 10 Mpbs and board running at 100.

Heapl 22928

Both it and virtual are fluctuating slightly at present but not by much.

So far it has passed the previous success limit of 444.

I will repeat the test on the faster speed again and run sin in.  But I have run it before and not noticed anything untoward?

Anything particular I should  look out for?

I am away to make a simple TCP server and client to run full packets at the board and echo them to test the interface more in line with the kind of tarf

post119482: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:43:54Z

I'm not familiar with python, but do you set any environment variables? I get an "ImportError: No module name os".

On 2019-02-05, 9:32 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Attached,



    Python 2.7

    Using standard python libs.



    Downloads a meg meg text file







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119480

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119481: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:33:47Z

Are you sure that this isn't a memory problem? If you run "sin in" intermittently on another console while you are running your ftp test, does the memory available stay the same or does it decrease?

On 2019-02-05, 9:29 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Python 2.7



    Downloads a 3 meg text file







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119479

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119480: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:32:18Z

Attached,

Python 2.7

Using standard python libs.

Downloads a meg meg text file

post119479: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:29:51Z

Python 2.7

Downloads a 3 meg text file

post119478: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:23:47Z

Please can you post your script as well?

On 2019-02-05, 9:16 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    Yeah sure



    So my system comes up with no network configured.  Everything is down.



    I then manually run



    Net &

    Net.e1000 -l1 &



    nameloc &



    Socket localhost &



    ifconfig lo0 localhost up

    ifconfig en1 144.179.1.199 netmask 255.255.255.0 up



    inetd



    I wait a few seconds between each step.  Speed of PC and board us 100 Mpbs FDX.  No switches in the way.



    Also for the last two iterations I have been running the second driver also Net.r6040 -l2 & launched after Net.e1000



    I then start a script running on PC which connects to FTP, does a 3 meg download, then uploads the same file and then disconnects.  Waits 1 second then repeats.



    Eventually it just stops responding to FTP and only way to recover it is to slay everything including Net and relaunch as above.



    When I ping from PC to card I can see from netinfo that packets are being recieved but the pings fail and board transmits nothing.











    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119477

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119477: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T14:16:31Z

Yeah sure

So my system comes up with no network configured.  Everything is down.

I then manually run

Net &

Net.e1000 -l1 &

nameloc &

Socket localhost &

ifconfig lo0 localhost up

ifconfig en1 144.179.1.199 netmask 255.255.255.0 up

inetd

I wait a few seconds between each step.  Speed of PC and board us 100 Mpbs FDX.  No switches in the way.

Also for the last two iterations I have been running the second driver also Net.r6040 -l2 & launched after Net.e1000

I then start a script running on PC which connects to FTP, does a 3 meg download, then uploads the same file and then disconnects.  Waits 1 second then repeats.

Eventually it just stops responding to FTP and only way to recover it is to slay everything including Net and relaunch as above.

When I ping from PC to card I can see from netinfo that packets are being recieved but the pings fail and board transmits nothing.

post119476: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T13:50:29Z

I'm just running "Net.e1000 -l2 -d1533" as it is the second interface on my machine. Can you send me the steps you run to reproduce the problem?

If the i210 and Vortex are sharing the same interrupt, are any other device using the same interrupt?

On 2019-02-05, 8:39 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    I have switched to another board and it runs better for still has the same issue eventually



    The board is a Adlink CM1-86DX3.  It has two interfaces one i210 and one R6040 (Vortex SoC).  They both share the same IRQ line.



    I dont know if this would factor into their being an issue,  Just done a test with both drivers running and e1000 configured with address.  Still fails.



    In your setups are you launching the Net.e1000 with any particular settings







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119475

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119475: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T13:39:10Z

I have switched to another board and it runs better for still has the same issue eventually

The board is a Adlink CM1-86DX3. It has two interfaces one i210 and one R6040 (Vortex SoC). They both share the same IRQ line.

I dont know if this would factor into their being an issue, Just done a test with both drivers running and e1000 configured with address. Still fails.

In your setups are you launching the Net.e1000 with any particular settings

post119473: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T12:36:16Z

I doubt very much that this is a driver problem, as the e1000 driver has been running at many sites for years. This rather sounds like a board/driver combination problem.

I have been running tests on the Net.e1000 4.25E for several hours at 100Mb/s without any problems. There isn't much we can do without hardware.

On 2019-02-05, 5:37 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    See below.  I am aware there is the newer driver in 2015 but I get the same issue with it also which is why i downgraded by 1 version to the one listed below.



    I ran test overnight with it running at 10 Mpbs FDX and did not encounter an issue after 2000 tests.  But at 100 Mpbs FDX it fails generally within 100 even with a bigger slug between each iteration of test (from 1 to 10 seconds as it is now)



    Everything else like Net I think is up to date.





    PROGRAM                 NAME         VERSION DATE

    sys/Proc32              Proc         4.25Q   Jul 18 2005

    sys/Slib32              Slib32       4.24B   Aug 12 1997

    /bin/Fsys               Fsys32       4.24Z   Jul 06 2009

    /bin/Fsys.atapi         atapi        4.25G   Jun 10 2010

    //1/bin/Dev32           Dev32        4.23G   Oct 04 1996

    //1/bin/Pipe            Pipe         4.23A   Feb 26 1996

    //1/bin/Dev32.ansi      Dev32.ansi   4.23H   Nov 21 1996

    //1/bin/Dev32.ser       Dev.ser      4.25A   Feb 14 2003

    //1/bin/Net             Net          4.25G   Jul 06 2010

    //1/bin/Net.e1000       Net.e1000    4.25D   Dec 19 2013

    //1/usr/ucb/Socket      Socket       4.25K   Feb 12 2003







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119472

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119472: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-05T10:37:27Z

See below.  I am aware there is the newer driver in 2015 but I get the same issue with it also which is why i downgraded by 1 version to the one listed below.

I ran test overnight with it running at 10 Mpbs FDX and did not encounter an issue after 2000 tests.  But at 100 Mpbs FDX it fails generally within 100 even with a bigger slug between each iteration of test (from 1 to 10 seconds as it is now)

Everything else like Net I think is up to date.

PROGRAM                 NAME         VERSION DATE

sys/Proc32              Proc         4.25Q   Jul 18 2005

sys/Slib32              Slib32       4.24B   Aug 12 1997

/bin/Fsys               Fsys32       4.24Z   Jul 06 2009

/bin/Fsys.atapi         atapi        4.25G   Jun 10 2010

//1/bin/Dev32           Dev32        4.23G   Oct 04 1996

//1/bin/Pipe            Pipe         4.23A   Feb 26 1996

//1/bin/Dev32.ansi      Dev32.ansi   4.23H   Nov 21 1996

//1/bin/Dev32.ser       Dev.ser      4.25A   Feb 14 2003

//1/bin/Net             Net          4.25G   Jul 06 2010

//1/bin/Net.e1000       Net.e1000    4.25D   Dec 19 2013

//1/usr/ucb/Socket      Socket       4.25K   Feb 12 2003

post119469: Re: Lockup problem with Net.e1000 Net.r6040

2019-02-04T18:32:40Z

Please can you post the output from "sin ver" on your system while running the e1000 driver?

Thanks, Hugh.

On 2019-02-04, 11:04 AM, "Paul Graham" <community-noreply@qnx.com> wrote:

    HI there



    I am currently attempting to evaluate QNX 4.25 on a Vortex DX3.  The SBC has two ethernet interfaces.  As such I am having issues with both of them.



    First point to note I am only ever running one driver at any given time.



    Net.e1000



    I bring it all up happily and then begin my test by ftping a file then uploading it again.  When it runs at 100 MBps/Full Duplex after about 60 to 100 operations the driver stops responding even to ping.



    I cannot ping out of the board either.



    I run trace log and get (55) NET raw app could not buffer pkt.



    Netinfo shows no errors of any kind and neither does netstat.



    The only way to bring it back up and working is to slay and relaunch everything including Net.



    I have verbose mode turned on for each and the driver -vvv



    Neither prints anything to console upon the error.



    I have already switched cables and removed the switch etc.



    Net.r6040



    This one is slightly more problematic.   Doing the same test as above with ping also running I suffer a lot of timeouts on ping.  I then run out test application which just echoe UDP packets back to a client.  And it times out as well.



    I have tried the released driver and a patched one from these forums in the 6040 post.



    Get the same issues on both.



    The r6040 is the onboard SOC one for the Vortex and the i210 is on the southbridge connected to it.



    Hoping someone may have insight



    Thanks in advance



    Paul







    _______________________________________________



    General

    http://community.qnx.com/sf/go/post119468

    To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119468: Lockup problem with Net.e1000 Net.r6040

2019-02-04T16:04:48Z

HI there

I am currently attempting to evaluate QNX 4.25 on a Vortex DX3.  The SBC has two ethernet interfaces.  As such I am having issues with both of them.

First point to note I am only ever running one driver at any given time.

Net.e1000

I bring it all up happily and then begin my test by ftping a file then uploading it again.  When it runs at 100 MBps/Full Duplex after about 60 to 100 operations the driver stops responding even to ping.

I cannot ping out of the board either.

I run trace log and get (55) NET raw app could not buffer pkt.

Netinfo shows no errors of any kind and neither does netstat.

The only way to bring it back up and working is to slay and relaunch everything including Net.

I have verbose mode turned on for each and the driver -vvv

Neither prints anything to console upon the error.

I have already switched cables and removed the switch etc.

Net.r6040

This one is slightly more problematic.   Doing the same test as above with ping also running I suffer a lot of timeouts on ping.  I then run out test application which just echoe UDP packets back to a client.  And it times out as well.

I have tried the released driver and a patched one from these forums in the 6040 post.

Get the same issues on both.

The r6040 is the onboard SOC one for the Vortex and the i210 is on the southbridge connected to it.

Hoping someone may have insight

Thanks in advance

Paul

post119397: Re: keyboard interrupt handler cause system hang on when press 'P' key

2019-01-09T11:55:50Z

Hello Cong,

Sorry for the delay with my answer. Can you attach full source example and compiler command line?

Respectfully,

Oleg

> Hello

>

> I have a keyboard interrupt handler ( attached file key_int.c bellow ).

> It was compiled and run ok on QNX 4.25 with almost keyboard, except only one

> case 'P' key.

>

> When I press 'P' key, the system is hanging on.

>

> Does anyone meet that situation? How can I do?

post119379: keyboard interrupt handler cause system hang on when press 'P' key

2019-01-03T03:05:20Z

Hello

I have a keyboard interrupt handler ( attached file key_int.c bellow ).

It was compiled and run ok on QNX 4.25 with almost keyboard, except only one case 'P' key.

When I press 'P' key, the system is hanging on.

Does anyone meet that situation? How can I do?

post119212: Re: Need a solution for USB keyboard interrupt key_scan

2018-10-12T17:00:45Z

Hi Cong,

Please request the package in the proper manner. In case of trouble getting this DDK, let me know and I’ll ask someone to review your request.

Respectfully,

Oleg

10 окт. 2018 г., в 11:34, Cong Pham <community-noreply@qnx.com> написал:

> Hi Mr Oleg,

>

> I have tried this link "http://www.qnx.com/download/group.html?programid=8692" to download USB DDK, but it looks like a long time approval process.

>

> I really need this usb ddk now, can you share it with me? If you can, please send to my email congpx@gmail.com.

>

> Thanks.

>

>

>> Hi Cong,

>>

>> You should't access to keyboard I/O-ports directly while driver is running.

>> Same here with USB driver. You can communicate with driver to test your

>> keyboard.

>>

>>> - QNX has USB driver deverlopment kits, where can I download it? Can someone

>> shared this USB DDK for QNX4 for me ?

>>

>> Latest USB DDK for QNX 4 is available here:

>>

>> http://www.qnx.com/download/group.html?programid=8692

>>

>> Respectfully,

>> Oleg

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post119199

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119205: Re: Net.r6040 network driver

2018-10-12T10:14:50Z

Hi Dhanya,

Can you post here your e-mail address? I'll send you driver for QNX 6.5.

Respectfully,

Oleg

21 сент. 2018 г., в 10:52:19, Dhanya Aravind <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Can you provide the source code of this driver? We need to use the same in QNX 6.5. We are currently using the older version of the driver and are seeing packet loss. Can you tell us what changed in this version?

>

> Thanks,

> Dhanya

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post119144

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119199: Re: Need a solution for USB keyboard interrupt key_scan

2018-10-10T08:34:53Z

Hi Mr Oleg,

I have tried this link "http://www.qnx.com/download/group.html?programid=8692" to download USB DDK, but it looks like a long time approval process.

I really need this usb ddk now, can you share it with me? If you can, please send to my email congpx@gmail.com.

Thanks.

> Hi Cong,

>

> You should't access to keyboard I/O-ports directly while driver is running.

> Same here with USB driver. You can communicate with driver to test your

> keyboard.

>

> > - QNX has USB driver deverlopment kits, where can I download it? Can someone

> shared this USB DDK for QNX4 for me ?

>

> Latest USB DDK for QNX 4 is available here:

>

> http://www.qnx.com/download/group.html?programid=8692

>

> Respectfully,

> Oleg

post119198: Re: Need a solution for USB keyboard interrupt key_scan

2018-10-09T10:37:43Z

Hi Cong,

You should't access to keyboard I/O-ports directly while driver is running. Same here with USB driver. You can communicate with driver to test your keyboard.

> - QNX has USB driver deverlopment kits, where can I download it? Can someone shared this USB DDK for QNX4 for me ?

Latest USB DDK for QNX 4 is available here:

http://www.qnx.com/download/group.html?programid=8692

Respectfully,

Oleg

9 окт. 2018 г., в 6:12:07, Cong Pham <community-noreply@qnx.com> написал:

> Hi,

>

> I have a keyboard test application. It gets keyboard interrupt and reads key-scan-code via qnx_hint_attach() and inp( 0x60 ), inp( 0x64) functions.

> It works fine for PS/2 keyboard (device: /dev/kbd).

>

> Now, when I change from PS/2 to USB keyboard, the new keyboard is running ok ( with drivers: io-usb, devu-usb and device: /dev/usbkbd0 ), but my test application does not run. It could not get any interrupt.

>

> - Is there any solution for testing usb keyboard?

> - QNX has USB driver deverlopment kits, where can I download it? Can someone shared this USB DDK for QNX4 for me ?

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post119197

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119197: Need a solution for USB keyboard interrupt key_scan

2018-10-09T03:12:07Z

Hi,

I have a keyboard test application. It gets keyboard interrupt and reads key-scan-code via qnx_hint_attach() and inp( 0x60 ), inp( 0x64) functions.

It works fine for PS/2 keyboard (device: /dev/kbd).

Now, when I change from PS/2 to USB keyboard, the new keyboard is running ok ( with drivers: io-usb, devu-usb and device: /dev/usbkbd0 ), but my test application does not run. It could not get any interrupt.

- Is there any solution for testing usb keyboard?

- QNX has USB driver deverlopment kits, where can I download it? Can someone shared this USB DDK for QNX4 for me ?

post119196: Re: How to display Cyrillic text CP-866 on a widget?

2018-10-09T03:01:34Z

Wap, thank to Mr Oleg,

Haiz, I have searched for some API functions to do it, but I did not found Px*() onces :(

I will try it.

Best regards.

post119195: Re: How to display Cyrillic text CP-866 on a widget?

2018-10-08T14:52:21Z

Hi Cong,

In your application you have to convert messages from CP866 to Unicode using PxTranslateToUTF() function. Read about this in Helpviewer. You also need Cyrillic fonts too, but it seems that you have installed them already.

Respectfully,

Oleg

5 окт. 2018 г., в 6:23:00, Cong Pham <community-noreply@qnx.com> написал:

> Hi

>

> I have written a Photon application A in QNX 4.25. In which, I setup a server to receive some messages from another process B. These messages are in Cyrillic text with OEM 866 codepage, what has read by process B from a file on disk, .

>

> So, I try to display the Cyrillic CP-866 string message to a widget via Pt_ARG_TEXT_STRING, but it can't.

> I also have changed some Pt_ARG_TEXT_FONT ( Helvetical, Arial, Tahoma, Helvetical Cyrillic..) but it can't .

> I have used fontcfg to istall Cyrillic fonts too.

>

> Now, how can I do???

>

> 1- Can I get some C/C++ function to convert CP866 to UTF-8 (on-the-fly) ? As on PED, I can open a CP866 encoding file and change it to UTF-8, but can I get its source code to build it myself ?

>

> 2- Do I need some FONT to display CP866 on Photon widget? what it is ?

>

> 3- Can I change the codepage of a TEXT or MULTITEXT widget?

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post119188

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119188: How to display Cyrillic text CP-866 on a widget?

2018-10-05T03:23:00Z

Hi

I have written a Photon application A in QNX 4.25. In which, I setup a server to receive some messages from another process B. These messages are in Cyrillic text with OEM 866 codepage, what has read by process B from a file on disk, .

So, I try to display the Cyrillic CP-866 string message to a widget via Pt_ARG_TEXT_STRING, but it can't.

I also have changed some Pt_ARG_TEXT_FONT ( Helvetical, Arial, Tahoma, Helvetical Cyrillic..) but it can't .

I have used fontcfg to istall Cyrillic fonts too.

Now, how can I do???

1- Can I get some C/C++ function to convert CP866 to UTF-8 (on-the-fly) ? As on PED, I can open a CP866 encoding file and change it to UTF-8, but can I get its source code to build it myself ?

2- Do I need some FONT to display CP866 on Photon widget? what it is ?

3- Can I change the codepage of a TEXT or MULTITEXT widget?

post119174: Re: Net.r6040 network driver

2018-10-01T10:23:10Z

Hi Dhanya,

Sorry for the delay with my answer. We should discuss about your question here.

Respectfully,

Oleg

21 сент. 2018 г., в 10:52:19, Dhanya Aravind <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Can you provide the source code of this driver? We need to use the same in QNX 6.5. We are currently using the older version of the driver and are seeing packet loss. Can you tell us what changed in this version?

>

> Thanks,

> Dhanya

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post119144

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119144: Re: Net.r6040 network driver

2018-09-21T07:52:19Z

Hi Oleg,

Can you provide the source code of this driver? We need to use the same in QNX 6.5. We are currently using the older version of the driver and are seeing packet loss. Can you tell us what changed in this version?

Thanks,

Dhanya

post119091: Re: Supporting both PS/2 and USB keyboard

2018-09-13T07:02:05Z

Thanks Oleg,

I will give it a try.

Best Regards,

Christian

post119090: Re: Supporting both PS/2 and USB keyboard

2018-09-12T09:59:41Z

Hello Christian,

I guess that you can use something like the following shell snippet:

devu-kbd &

...

if [ -f /dev/usbkbd0 ] ; then

Dev32.ansi ... -d /dev/usbkbd0 &

else

Dev32.ansi ... &

fi

...

Respectfully,

Oleg

12 сент. 2018 г., в 0:27:59, Christian Friberg <community-noreply@qnx.com> написал:

> We provide a QNX 4.25 based application on a bootable CD-ROM with a text console installation script where some choices are made during installation to select the correct OS and application configuration.

> We also supply the computers for this application and have so far always been able to use computers with PS/2 ports and find suitable PS/2 keyboards. However, this is getting harder nowadays.

>

> So, we are looking into adding USB keyboard support to our OS image using the "new" Dev32.ansi driver.

> But, if at all possible we would like to have the same bootable installation CD-ROM support both older computers with PS/2 keyboards as well as new ones with USB keyboard in order to reduce number of software products to support.

>

> Is there a recommended way to do this?

>

> I basically need to start Dev.ansi with or without the USB-related parameters depending on whether there is a USB keyboard connected or not. (along with io-usb and USB keyboard driver of course).

> The main problem seems to be keyboard support in console mode - once in QNX Windows the USB keyboard works fine. My first approach was to detect USB keyboard using "usb" utility and if found, then slay old Dev.ansi and instead start Dev32.ansi etc.

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post119089

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post119089: Supporting both PS/2 and USB keyboard

2018-09-11T21:27:59Z

We provide a QNX 4.25 based application on a bootable CD-ROM with a text console installation script where some choices are made during installation to select the correct OS and application configuration.

We also supply the computers for this application and have so far always been able to use computers with PS/2 ports and find suitable PS/2 keyboards. However, this is getting harder nowadays.

So, we are looking into adding USB keyboard support to our OS image using the "new" Dev32.ansi driver.

But, if at all possible we would like to have the same bootable installation CD-ROM support both older computers with PS/2 keyboards as well as new ones with USB keyboard in order to reduce number of software products to support.

Is there a recommended way to do this?

I basically need to start Dev.ansi with or without the USB-related parameters depending on whether there is a USB keyboard connected or not. (along with io-usb and USB keyboard driver of course).

The main problem seems to be keyboard support in console mode - once in QNX Windows the USB keyboard works fine. My first approach was to detect USB keyboard using "usb" utility and if found, then slay old Dev.ansi and instead start Dev32.ansi etc.

post118839: Re: Can´t install QNX4...

2018-05-22T14:41:25Z

Is QNX4 no longer function with the new motherboard chipsets ? Any update ? I really appreciate any help.

Víctor J Gamboa

post118799: Can´t install QNX4...

2018-05-05T17:05:03Z

Hi! I am trying to install QNX4 on a new machine, to replace an old one, but the new motherboards only has AHCI support for SATA drives. So, I installed QNX 4 Product Suite 2015 on an old machine, I installed Proc32 updates (QNX425-Proc32-425R-20161101.tar.gz), the build file has: /boot/sys/Proc32

$ /boot/sys/Proc32 -E0 -l 1

/bin/Fsys.ahci

$ /bin/Fsys.ahci fsys -Ndsk0 -n0=hd0.

I put on the new machine but it didn't work. I attach the error image.

I really appreciate any help to install QNX4 on a machine with only has AHCI support, because the motherboards don't have Atapi support any more. Thank you in advance for any help.

Víctor J Gamboa

post118661: Re: Access needs of hard drive

2018-03-12T08:11:48Z

Hello Raghu,

You can work directly with /dev/hd* to get raw access to a whole hard drive or /dev/hd?t* to raw access to a specific partition. Keep in mind that raw access to hard drive and particularly to mounted partition is dangerous operation.

Respectfully,

Oleg

8 марта 2018 г., в 8:23:35, Raghu Venugopalan(deleted) <community-noreply@qnx.com> написал:

> Hi,

> I needed information on how we can find the access (read/write) needs of the hard drive. One way I was looking is getting information from the fsys driver in QNX4.25 which is used to read and write to hard disk. But I could not find any literature on how to do this. Please let me know if there is a way to get this information.

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118657

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118657: Access needs of hard drive

2018-03-08T05:23:35Z

Hi,

I needed information on how we can find the access (read/write) needs of the hard drive. One way I was looking is getting information from the fsys driver in QNX4.25 which is used to read and write to hard disk. But I could not find any literature on how to do this. Please let me know if there is a way to get this information.

post118653: Re: USB input device of photon

2018-03-05T16:15:33Z

Have you tried a wildcard in the commands ie... mouse* instead of mouse0 ?

Not sure if will work but its worth a shot.

post118616: Re: ARP Behavior for TCPIP 5.0 on QNX 4.25

2018-02-23T14:35:30Z

Hello Robert,

Have you tested TCP/IP 5.10 components? Please install the latest QNX 4 Product Suite CD 2015 and and updated Tcpip manager from the following web page:

http://community.qnx.com/sf/wiki/do/viewPage/projects.qnx4/wiki/LatestSoftwareUpdates

Respectfully,

Oleg

23 февр. 2018 г., в 1:51, Robert McGaughey <community-noreply@qnx.com> написал:

> We have experienced several cases where QNX 4.25 did not ACK incoming TCP packets nor did it transmit any new TCP packets while an ARP refresh was in progress. We noticed this behavior because we also encountered a problem with our remote device where the driver stopped processing incoming messages for 31 seconds.

>

> From the Wireshark analysis, it appears as if the ARP mechanism in TCPIP 5.0 on QNX 4.25 deletes the ARP table cache entry when it expires, sends an ARP broadcast request, and waits until it receives the response back from the remote device before it allows any TCP messages to be transmitted. Can anyone confirm if this is expected behavior for the ARP refresh on QNX 4.25 or have we encountered another bug in the TCP/IP stack?

>

> Thanks,

>

> Robert

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118614

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118614: ARP Behavior for TCPIP 5.0 on QNX 4.25

2018-02-22T22:51:48Z

We have experienced several cases where QNX 4.25 did not ACK incoming TCP packets nor did it transmit any new TCP packets while an ARP refresh was in progress. We noticed this behavior because we also encountered a problem with our remote device where the driver stopped processing incoming messages for 31 seconds.

From the Wireshark analysis, it appears as if the ARP mechanism in TCPIP 5.0 on QNX 4.25 deletes the ARP table cache entry when it expires, sends an ARP broadcast request, and waits until it receives the response back from the remote device before it allows any TCP messages to be transmitted. Can anyone confirm if this is expected behavior for the ARP refresh on QNX 4.25 or have we encountered another bug in the TCP/IP stack?

Thanks,

Robert

post118499: RE: Chinese SimSun font on phindows

2018-01-31T10:42:11Z

Thanks Oleg.

-----Original Message-----

From: Олег Большаков [mailto:community-noreply@qnx.com]

Sent: 31 January 2018 10:08

To: general-qnx4@community.qnx.com

Subject: Re: Chinese SimSun font on phindows

Hi Pete,

If your Windows program is not UTF-8 compatible then you shouldn't send UTF-8 data to it. You can convert UTF-8 to encoding that is supported by Windows program.

Respectfully,

Oleg

30 янв. 2018 г., в 20:07:32, Pete Mackereth <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Just on the topic of Unicode support we have a system that transfers data over a tcp connection to windows that uses the printf command in a C program. This program is not UTF-8 compliant and obviously the result is gibberish on the windows side when sending Chinese characters. Do you know of an easy way of making this UTF-8 compatible under QNX4.25?

>

> Regards,

> Pete

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118494

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

_______________________________________________

General

http://community.qnx.com/sf/go/post118497

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118497: Re: Chinese SimSun font on phindows

2018-01-31T10:28:23Z

Hi Pete,

If your Windows program is not UTF-8 compatible then you shouldn't send UTF-8 data to it. You can convert UTF-8 to encoding that is supported by Windows program.

Respectfully,

Oleg

30 янв. 2018 г., в 20:07:32, Pete Mackereth <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Just on the topic of Unicode support we have a system that transfers data over a tcp connection to windows that uses the printf command in a C program. This program is not UTF-8 compliant and obviously the result is gibberish on the windows side when sending Chinese characters. Do you know of an easy way of making this UTF-8 compatible under QNX4.25?

>

> Regards,

> Pete

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118494

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118494: Re: Chinese SimSun font on phindows

2018-01-30T17:07:32Z

Hi Oleg,

Just on the topic of Unicode support we have a system that transfers data over a tcp connection to windows that uses the printf command in a C program. This program is not UTF-8 compliant and obviously the result is gibberish on the windows side when sending Chinese characters. Do you know of an easy way of making this UTF-8 compatible under QNX4.25?

Regards,

Pete

post118493: Re: Chinese SimSun font on phindows

2018-01-30T15:34:31Z

Hi Oleg,

Thanks for trying, I thought it was a bit of a long shot.

Regards,

Pete

post118477: Re: Chinese SimSun font on phindows

2018-01-26T13:09:37Z

Hello Pete,

Sorry for the delay with my answer. We have reproduced this issue and have tried to find solution. Unfortunately it seems that TTF fonts will work correctly with both updated Phindows and phrelay. Updated phrelay is available for QNX 6.5.0 only. There is no such update for QNX 4.25. It seems that you can use only PHF fonts with Phindows.

Respectfully,

Oleg

19 янв. 2018 г., в 16:56:19, Pete Mackereth <community-noreply@qnx.com> написал:

> Hello,

>

> We have a system that's been created using the latest version of the QNX4.25 Product Suite, we have obtained a Chinese Supplement license and have created a nice little Chinese system using the Chinese fonts supplied. To me it looks good but I have been told by one of our Chinese colleagues it is not acceptable.

>

> We have downloaded the SimSun .ttf file and have installed this and it looks great, the problem is phindows will not show it, I think older versions of phindows have problems with scalable fonts.

>

> Is there anything we can do? Can we upgrade to a later version of phindows?

>

> Thanks and regards,

> Pete

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118408

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118474: Re: NFS V3/V4

2018-01-26T08:11:12Z

Hello!

Unfortunately, QNX 4 supports NFS v2 only.

Respectfully,

Oleg

26 янв. 2018 г., в 2:04:35, M. Leippert(deleted) <community-noreply@qnx.com> написал:

> I try to connect from QNX 4 to a NAS server using NFS.

> I get the message "Protocol not supported".

> rpcinfo shows that the NAS supports NFS V3 and NFS V4.

> rpcinfo shows that the QNX machine only supports NFS V2.

>

> Is it possible to have NFS V3 or NFS V4 on a QNX 4 machine?

>

> Best regards, Werner

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118473

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118473: NFS V3/V4

2018-01-25T23:04:35Z

I try to connect from QNX 4 to a NAS server using NFS.

I get the message "Protocol not supported".

rpcinfo shows that the NAS supports NFS V3 and NFS V4.

rpcinfo shows that the QNX machine only supports NFS V2.

Is it possible to have NFS V3 or NFS V4 on a QNX 4 machine?

Best regards, Werner

post118408: Chinese SimSun font on phindows

2018-01-19T13:56:19Z

Hello,

We have a system that's been created using the latest version of the QNX4.25 Product Suite, we have obtained a Chinese Supplement license and have created a nice little Chinese system using the Chinese fonts supplied. To me it looks good but I have been told by one of our Chinese colleagues it is not acceptable.

We have downloaded the SimSun .ttf file and have installed this and it looks great, the problem is phindows will not show it, I think older versions of phindows have problems with scalable fonts.

Is there anything we can do? Can we upgrade to a later version of phindows?

Thanks and regards,

Pete

post118401: Re: PxImage linking error

2018-01-18T02:12:13Z

Yep Mr Oleg,

Thank for your suggestion. It's work!

post118398: RE: Siemens IPC347E Graphics driver

2018-01-17T12:12:29Z

Thanks Oleg.

-----Original Message-----

From: Олег Большаков [mailto:community-noreply@qnx.com]

Sent: 17 January 2018 11:50

To: general-qnx4@community.qnx.com

Subject: Re: Siemens IPC347E Graphics driver

Hi Pete,

Pg.flat* is a driver family that provides support for the most graphics controllers. Modern graphics controllers often don't support 8-, 15- and 16-bit color modes, so Pg.flatdc32 is the best choice in that case.

Respectfully,

Oleg

17 янв. 2018 г., в 13:47:34, Pete Mackereth <community-noreply@qnx.com> написал:

> Hello,

>

> I've found a driver that works ... Pg.flatdc32.

>

> Thanks,

> Pete

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118396

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

_______________________________________________

General

http://community.qnx.com/sf/go/post118397

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118397: Re: Siemens IPC347E Graphics driver

2018-01-17T12:11:02Z

Hi Pete,

Pg.flat* is a driver family that provides support for the most graphics controllers. Modern graphics controllers often don't support 8-, 15- and 16-bit color modes, so Pg.flatdc32 is the best choice in that case.

Respectfully,

Oleg

17 янв. 2018 г., в 13:47:34, Pete Mackereth <community-noreply@qnx.com> написал:

> Hello,

>

> I've found a driver that works ... Pg.flatdc32.

>

> Thanks,

> Pete

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118396

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118396: Re: Siemens IPC347E Graphics driver

2018-01-17T10:47:34Z

Hello,

I've found a driver that works ... Pg.flatdc32.

Thanks,

Pete

post118392: Siemens IPC347E Graphics driver

2018-01-16T17:40:42Z

Hello,

I've loaded this PC with the latest QNX 4.25 product suite and now I'm having problems with the video driver, I've tried quite a number and none of them work as required.

I've attached a show_pci dump for help.

Any ideas?

Thanks and regards,

Pete

post118388: Re: PxImage linking error

2018-01-16T10:27:22Z

Cong,

You have to define both PX_IMAGE_MODULES and desired PX_XXX_SUPPORT macros to enable PXImage functionality. You can add the following line to your mf.7 file just after CFLAGS = ...

CFLAGS += -DPX_IMAGE_MODULES -DPX_GIF_SUPPORTED

The list of supported PX modules you can find in QNX Help Viewer in PxLoadImage() overview.

Respectfully,

Oleg

16 янв. 2018 г., в 12:34:02, Cong Pham <community-noreply@qnx.com> написал:

> Hi,

>

> Here, this issue will appears with all functions which called.

>

> on QNX 4.25 with Watcom C/C++ compiler 10.6 installed frome lasted CD (build 2015).

>

>

>

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118387

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

> <pton7.cc><mf.7>

post118387: Re: PxImage linking error

2018-01-16T09:34:02Z

Hi,

Here, this issue will appears with all functions which called.

on QNX 4.25 with Watcom C/C++ compiler 10.6 installed frome lasted CD (build 2015).

post118386: Re: PxImage linking error

2018-01-16T09:07:44Z

Hi Cong,

Can you attach a small complete source example that illustrates the issue?

Respectfully,

Oleg

15 янв. 2018 г., в 5:27:17, Cong Pham <community-noreply@qnx.com> написал:

> Hi everyone,

>

> On the lastest QNX 4.25 build:

>

> I have compiled a source-code file using PxImage lib.

> I have #include <photon/PxImage.h> in the source file.

> I have full options for linking libraries: -l Aplib -l phrtlib -l phexlib -l phcontrib -l photon_s -l phrender_s

>

> But, when linking, it show error:

> warning(1028): _PxImageFunc is an undefined reference

> file /usr/lib/phexlib3r.lib(/src/photon/lib/exlib/PxImage.c): undefined symbol _PxImageFunc

> (see my attached file below)

> I have written PxImageFunc() myself on my code, but it happends again :)

>

> So, how can I do?

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118376

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

> <PxImageFunc.png>

post118376: PxImage linking error

2018-01-15T02:27:17Z

Hi everyone,

On the lastest QNX 4.25 build:

I have compiled a source-code file using PxImage lib.

I have #include <photon/PxImage.h> in the source file.

I have full options for linking libraries: -l Aplib -l phrtlib -l phexlib -l phcontrib -l photon_s -l phrender_s

But, when linking, it show error:

warning(1028): _PxImageFunc is an undefined reference

file /usr/lib/phexlib3r.lib(/src/photon/lib/exlib/PxImage.c): undefined symbol _PxImageFunc

(see my attached file below)

I have written PxImageFunc() myself on my code, but it happends again :)

So, how can I do?

post118253: Re: USB input device of photon

2017-11-30T12:52:26Z

Hi Ulrich,

QNX 4 doesn't support hotplugging. But it is possible to implement your own specific hotplugging manager. You can parse usb utility output in your shell script to catch insertion of HID devices and relaunch Input. Also you can use USB SDK to develop manager that can monitor USB events.

Respectfully,

Oleg

29 нояб. 2017 г., в 11:31:20, Mailaender, Ulrich <community-noreply@qnx.com> написал:

> Hi,

>

> I am using usb-keyboard and usb-mouse as input device of photon. If I boot the PC everything is ok, keyboard and mouse working fine.

> If I unplug the mouse and plug it in again, the mouse is not working anymore.

>

> sysint:

> #io-usb

> #devu-mouse

> #devu-kbd

>

> input.xx:

> kbd –R fd-dev-usbkbd0 msoft fd –d/dev/usbmouse0

>

> I noticed, after plug in the mouse again there is a new /dev/mouse1.

> The Input is still looking for /dev/mouse0.

>

> I am able to fix this manual:

> slay devu-mouse

> devu-mouse &

> Input msoft fd –d/dev/mouse0

>

> After that, mouse is working.

> But I need a solution without any manual operation.

>

> Is there a solution??

>

> Regards

>

> Ulrich Mailänder

>

> <Вложенный файл Почты.html>

post118248: USB input device of photon

2017-11-29T08:53:26Z

Hi,

I am using usb-keyboard and usb-mouse as input device of photon. If I boot the PC everything is ok, keyboard and mouse working fine.

If I unplug the mouse and plug it in again, the mouse is not working anymore.

sysint:

#io-usb

#devu-mouse

#devu-kbd

input.xx:

kbd -R fd-dev-usbkbd0 msoft fd -d/dev/usbmouse0

I noticed, after plug in the mouse again there is a new /dev/mouse1.

The Input is still looking for /dev/mouse0.

I am able to fix this manual:

slay devu-mouse

devu-mouse &

Input msoft fd -d/dev/mouse0

After that, mouse is working.

But I need a solution without any manual operation.

Is there a solution??

Regards

Ulrich Mailänder

post118242: Re: memory leak snmp

2017-11-27T12:22:50Z

Hi Ulrich,

It seems a bit strange, but if it's okay for you then I won't check it.

Respectfully,

Oleg

27 нояб. 2017 г., в 13:47:22, Ulrich Mailänder <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> I have done some tests. If I slow down the for loop, no memory leak appears.

> So I simply add a delay of 100ms, and everything is ok now.

>

> Regards

> Ulrich

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118241

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118241: Re: RE: memory leak snmp

2017-11-27T10:47:22Z

Hi Oleg,

I have done some tests. If I slow down the for loop, no memory leak appears.

So I simply add a delay of 100ms, and everything is ok now.

Regards

Ulrich

post118207: Re: Not received trial license key

2017-11-16T12:58:37Z

Hello!

It seems that you answered wrong address. Please contact your regional sales representative.

Respectfully,

Oleg

15 нояб. 2017 г., в 19:37:43, yo kay <community-noreply@qnx.com> написал:

> Our records indicate that you've already requested a license key to participate in our free 30-day product evaluation program. If you are interested in extending your evaluation, please contact your regional sales representative.

>

> But i have not received license key.

>

> Please help me.

>

> Thanks.

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118206

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118206: Not received trial license key

2017-11-15T16:37:43Z

Our records indicate that you've already requested a license key to participate in our free 30-day product evaluation program. If you are interested in extending your evaluation, please contact your regional sales representative.

But i have not received license key.

Please help me.

Thanks.

post118205: RE: memory leak snmp

2017-11-15T13:37:50Z

Hi Oleg,

I try to do a simple program but this takes time. So in the meantime a short description of the program

init_mib()

for ( ... )

{

snmp_synch_setup ();

if ( snmp_open (...))

{

snmp_pdu_create (...);

read_objid (...);

snmp_add_null_var (...);

snmp_synch_response (...);

snmp_free_pdu (...);

snmp_close (...);

}

}

Regards

Ulrich

-----Original Message-----

From: Олег Большаков [mailto:community-noreply@qnx.com]

Sent: Wednesday, November 15, 2017 11:49 AM

To: general-qnx4@community.qnx.com

Subject: Re: memory leak snmp

Hello Ulrich,

The snmp_open() call uses malloc() to allocate memory for internal data. Don't you forget to call snmp_close()? If not then can you post here tarball with minimal working example that illustrates the problem?

Respectfully,

Oleg

14 нояб. 2017 г., в 13:48:12, Mailaender, Ulrich <community-noreply@qnx.com> написал:

> Hello QNX admins,

>

> I am using snmp to read some information from an external device. Therefore I link snmp3r.lib and socket3r.lib so I am able to use function snmp_open (), ….

> There is no problem with the function itself. The problem is, the DATA memory is increasing all the time!!

> Is there any update or other solution about this problem??

>

> (using tcp/ip version 5.1)

>

> BR Ulrich

_______________________________________________

General

http://community.qnx.com/sf/go/post118204

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118204: Re: memory leak snmp

2017-11-15T11:11:43Z

Hello Ulrich,

The snmp_open() call uses malloc() to allocate memory for internal data. Don't you forget to call snmp_close()? If not then can you post here tarball with minimal working example that illustrates the problem?

Respectfully,

Oleg

14 нояб. 2017 г., в 13:48:12, Mailaender, Ulrich <community-noreply@qnx.com> написал:

> Hello QNX admins,

>

> I am using snmp to read some information from an external device. Therefore I link snmp3r.lib and socket3r.lib so I am able to use function snmp_open (), ….

> There is no problem with the function itself. The problem is, the DATA memory is increasing all the time!!

> Is there any update or other solution about this problem??

>

> (using tcp/ip version 5.1)

>

> BR Ulrich

post118199: memory leak snmp

2017-11-14T11:10:33Z

Hello QNX admins,

I am using snmp to read some information from an external device. Therefore I link snmp3r.lib and socket3r.lib so I am able to use function snmp_open (), ....

There is no problem with the function itself. The problem is, the DATA memory is increasing all the time!!

Is there any update or other solution about this problem??

(using tcp/ip version 5.1)

BR Ulrich

post118186: RE: Siemens IPC347E

2017-11-07T09:55:41Z

Hi Oleg,

Thanks for the response, I thought it is was probably OK, just checking. The thing is we can't check before we buy we just have to jump in and take the hit.

Regards,

Pete

-----Original Message-----

From: Олег Большаков [mailto:community-noreply@qnx.com]

Sent: 06 November 2017 21:08

To: general-qnx4@community.qnx.com

Subject: Re: Siemens IPC347E

Hi Pete,

It seems that the IPC347E based on Intel H61, so it should be works fine with the latest QNX 4 Install CD Experimental 2015. But it’s better to check the PC before purchasing if possible.

Respectfully,

Oleg

3 нояб. 2017 г., в 19:46, Pete Mackereth <community-noreply@qnx.com> написал:

> Hello,

>

> I am thinking of using the Siemens IPC347E with QNX 4.25, any ideas if there will be any issues, here is the link ...

>

> https://w3.siemens.com/mcms/pc-based-automation/en/industrial-pc/rack-pc/simatic-ipc347e/Pages/Default.aspx

>

> See also attached config details.

>

> Thanks,

> Pete

>

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118180

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

> <Spec.png>

_______________________________________________

General

http://community.qnx.com/sf/go/post118185

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118185: Re: Siemens IPC347E

2017-11-06T21:30:30Z

Hi Pete,

It seems that the IPC347E based on Intel H61, so it should be works fine with the latest QNX 4 Install CD Experimental 2015. But it’s better to check the PC before purchasing if possible.

Respectfully,

Oleg

3 нояб. 2017 г., в 19:46, Pete Mackereth <community-noreply@qnx.com> написал:

> Hello,

>

> I am thinking of using the Siemens IPC347E with QNX 4.25, any ideas if there will be any issues, here is the link ...

>

> https://w3.siemens.com/mcms/pc-based-automation/en/industrial-pc/rack-pc/simatic-ipc347e/Pages/Default.aspx

>

> See also attached config details.

>

> Thanks,

> Pete

>

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118180

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

> <Spec.png>

post118180: Siemens IPC347E

2017-11-03T16:46:09Z

Hello,

I am thinking of using the Siemens IPC347E with QNX 4.25, any ideas if there will be any issues, here is the link ...

https://w3.siemens.com/mcms/pc-based-automation/en/industrial-pc/rack-pc/simatic-ipc347e/Pages/Default.aspx

See also attached config details.

Thanks,

Pete

post118080: Re: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

2017-09-27T01:46:13Z

Any progress on this issue? This is becoming very urgent.

post118024: Re: Net runtime errors

2017-09-08T12:18:46Z

Thanks Oleg.

Ray

post118023: Re: Net runtime errors

2017-09-08T11:30:01Z

Hi Ray,

More detailed information you can get from Proc's trace buffer using traceinfo utility, for example:

# traceinfo -e /etc/config/trace.net -M4

7 — failed vc_attach ctrl pkt

35 — Node not in nodemap

56 — netmap entry added by driver

Usually these messages are not errors, but diagnostic messages.

Respectfully,

Oleg

7 сент. 2017 г., в 18:04:33, ray t <community-noreply@qnx.com> написал:

> Hi,

>

> When I run Net -vvv & I get

>

> "Net Runtime Error 0035 Net: Runtime Error 0007" continuously output to console

>

> I also get Net: Runtime Error 0056 once after running Net.rtl8169

>

> I am using Net from latest installation CD

>

> What do these error codes mean ?

>

> Thanks,

>

> Ray

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post118021

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post118021: Net runtime errors

2017-09-07T15:04:33Z

Hi,

When I run Net -vvv & I get

"Net Runtime Error 0035 Net: Runtime Error 0007" continuously output to console

I also get Net: Runtime Error 0056 once after running Net.rtl8169

I am using Net from latest installation CD

What do these error codes mean ?

Thanks,

Ray

post117969: Re: XGI Volari Z9S graphics chip

2017-08-22T11:01:25Z

Hello Ray,

The most of currently available graphics controllers for x86 are VESA compatible. So Z9S should be work with vesa too. But it's better to test how controller works with QNX before the purchasing if it's possible.

Respectfully,

Oleg

> There is no QNX4 driver for this GPU, does anyone know if this GPU is VESA

> compatible ?

>

> Thanks,

>

> Ray

post117966: Re: XGI Volari Z9S graphics chip

2017-08-20T13:32:35Z

I have found a datasheet for Z9M which suggests it is VESA compliant..........

"Supports VESA standard super high resolution graphics modes"

Not sure if Z9S is compatible with Z9M ?

Any feedback appreciated.

Thanks,

Ray

post117965: XGI Volari Z9S graphics chip

2017-08-20T13:27:21Z

There is no QNX4 driver for this GPU, does anyone know if this GPU is VESA compatible ?

Thanks,

Ray

post117946: RE: Dev32.ser MEMIO

2017-08-08T13:04:22Z

A colleague of mine made some tests.

Fred:

How was the test of the Dev.ser development from QNX for the PCIe of AddiData?

BR, Klaus

-----Original Message-----

From: Oleg Bolshakov [mailto:community-noreply@qnx.com]

Sent: Tuesday, August 08, 2017 2:58 PM

To: general-qnx4

Subject: Re: Dev32.ser MEMIO

Hi Klaus,

Did you try the driver that I've attached in my last message? How does it work on your hardware?

Respectfully,

Oleg

> I can make the tests. If you have a Dev32.ser with the code extension

> from AddiData.

> Of course I can send you one if that will help.

> BR, Klaus

_______________________________________________

General

http://community.qnx.com/sf/go/post117945

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117945: Re: Dev32.ser MEMIO

2017-08-08T12:58:19Z

Hi Klaus,

Did you try the driver that I've attached in my last message? How does it work on your hardware?

Respectfully,

Oleg

> I can make the tests. If you have a Dev32.ser with the code extension from

> AddiData.

> Of course I can send you one if that will help.

> BR, Klaus

post117942: Re: DM&P EBOX / Vortex DX2

2017-08-03T17:11:23Z

Hi Oleg,

Thanks for the quick response.

I have had to use Hydra/flat in he past so hopefully it will be OK this

time.

I will keep you and the community posted on how we get on with the hardware.

Regards,

Ray

On 03/08/2017 16:45, Олег Большаков wrote:

> Hi Ray,

>

> Usually it's possible to make Hydra.ms / Pg.flat* driver working without hardware acceleration. But it’s best to test the hardware before the purchasing.

>

> Respectfully,

> Oleg

>

> 2 авг. 2017 г., в 12:43, ray t <community-noreply@qnx.com> написал:

>

>> Dear QNX4 Community,

>>

>> I am looking into using a DM&P EBOX DIN PC-333X which uses the Vortex 86DX2 SOC

>>

>> I am confident that network will be OK as it uses RDC R6040 which has a QNX4 driver.

>>

>> Despite my best efforts I can't find out what graphics chip it uses, has anyone used this SOC or similar, ie Vortex DX, MX etc. with Photon.

>>

>> I am not concerned about hardware acceleration just 800x600 SVGA.

>>

>> Thanks,

>>

>> Ray

>>

>>

>>

>>

>>

>> _______________________________________________

>>

>> General

>> http://community.qnx.com/sf/go/post117938

>> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117940

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117941: Re: DM&P EBOX / Vortex DX2

2017-08-03T17:06:42Z

Hi Oleg,

Thanks for your quick reply.

Hydra/flat has worked in the past so hopefully it will this time !

I am waiting for the hardware to arrive, once I have finished our tests I will post our findings so the community will know how QNX4 compatible it is.

Regards,

Ray

post117940: Re: DM&P EBOX / Vortex DX2

2017-08-03T15:45:36Z

Hi Ray,

Usually it's possible to make Hydra.ms / Pg.flat* driver working without hardware acceleration. But it’s best to test the hardware before the purchasing.

Respectfully,

Oleg

2 авг. 2017 г., в 12:43, ray t <community-noreply@qnx.com> написал:

> Dear QNX4 Community,

>

> I am looking into using a DM&P EBOX DIN PC-333X which uses the Vortex 86DX2 SOC

>

> I am confident that network will be OK as it uses RDC R6040 which has a QNX4 driver.

>

> Despite my best efforts I can't find out what graphics chip it uses, has anyone used this SOC or similar, ie Vortex DX, MX etc. with Photon.

>

> I am not concerned about hardware acceleration just 800x600 SVGA.

>

> Thanks,

>

> Ray

>

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117938

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117938: DM&P EBOX / Vortex DX2

2017-08-02T09:43:38Z

Dear QNX4 Community,

I am looking into using a DM&P EBOX DIN PC-333X which uses the Vortex 86DX2 SOC

I am confident that network will be OK as it uses RDC R6040 which has a QNX4 driver.

Despite my best efforts I can't find out what graphics chip it uses, has anyone used this SOC or similar, ie Vortex DX, MX etc. with Photon.

I am not concerned about hardware acceleration just 800x600 SVGA.

Thanks,

Ray

post117897: Re: Czech language support

2017-07-20T07:02:52Z

Hello Oleg,

Thanks for the response.

I can do this, I just wanted to know that there will not be any conflict in case that system has undocumented definitions.

BR Sara

post117889: Re: Czech language support

2017-07-19T12:46:11Z

Hi Sara,

There is not standard the environmental variable definition, keyboard extension and translation file extension for Czech. Same here for some other languages from the list. But you can use cs_CZ for this. Just add to your languages.def the following line:

---

l=Czech,cs_CZ

---

Also you can add your own keyboard layout to /qnx4/photon/keyboard/ using existed files and sample.kdef.

Respectfully,

Oleg

18 июля 2017 г., в 17:31:52, Sara Zukovsky <community-noreply@qnx.com> написал:

> Hello Oleg,

>

> In 'Languages supported' section Czech is mentioned along with Slovak:

> ----------------------------------

> By adding the Photon Extended Latin set (latinx.pfr), the developer can support several additional languages, including:

> Afrikaans

> Basque

> Catalan

> Croatian

> Czech

> Esperanto

> Estonian

> Greenlandic

> Hungarian

> Latvian

> Lithuanian

> Maltese

> Polish

> Romanian

> Slovak

> Turkish

> Welsh

> ----------------------------------

>

> But while in 'International Language support' section for Slovak language there is following definition, for Czech it is not provided:

> ----------------------------------

> Running your application

>

> In order for the PhAB API to know which translation file you want to use, you must set the ABLANG environment variable to one of the values below:

>

> Language: Value:

> Slovak sk_SK

> ----------------------------------

>

> And in system 'languages.def' file:

> ----------------------------------

> l=Belgian French,fr_BE

> l=Canadian English,en_CA

> l=Canadian French,fr_CA

> l=Danish,da_DK

> l=Dutch,nl_NL

> l=French,fr_FR

> l=German,de_DE

> l=Italian,it_IT

> l=Japanese,ja_JP

> l=Norwegian,no_NO

> l=Portuguese,pt_PT

> l=Polish,pl_PL

> l=Swiss French,fr_CH

> l=Swiss German,de_CH

> l=Slovak,sk_SK

> l=Spanish,es_ES

> l=Swedish,se_SE

> l=UK English,en_GB

> l=USA English,en_US

> l=Macedonian,mc_MC

> ----------------------------------

> BR Sara

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117888

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117888: Re: Czech language support

2017-07-18T14:31:52Z

Hello Oleg,

In 'Languages supported' section Czech is mentioned along with Slovak:

----------------------------------

By adding the Photon Extended Latin set (latinx.pfr), the developer can support several additional languages, including:

Afrikaans

Basque

Catalan

Croatian

Czech

Esperanto

Estonian

Greenlandic

Hungarian

Latvian

Lithuanian

Maltese

Polish

Romanian

Slovak

Turkish

Welsh

----------------------------------

But while in 'International Language support' section for Slovak language there is following definition, for Czech it is not provided:

----------------------------------

Running your application

In order for the PhAB API to know which translation file you want to use, you must set the ABLANG environment variable to one of the values below:

Language: Value:

Slovak sk_SK

----------------------------------

And in system 'languages.def' file:

----------------------------------

l=Belgian French,fr_BE

l=Canadian English,en_CA

l=Canadian French,fr_CA

l=Danish,da_DK

l=Dutch,nl_NL

l=French,fr_FR

l=German,de_DE

l=Italian,it_IT

l=Japanese,ja_JP

l=Norwegian,no_NO

l=Portuguese,pt_PT

l=Polish,pl_PL

l=Swiss French,fr_CH

l=Swiss German,de_CH

l=Slovak,sk_SK

l=Spanish,es_ES

l=Swedish,se_SE

l=UK English,en_GB

l=USA English,en_US

l=Macedonian,mc_MC

----------------------------------

BR Sara

post117887: Re: Czech language support

2017-07-18T13:58:03Z

Hi Sara,

Can you post here a quote from documentation? I guess it means that Czech language is supported by fonts.

Respectfully,

Oleg

16 июля 2017 г., в 11:12:33, Sara Zukovsky <community-noreply@qnx.com> написала:

> According to QNX 4 documentation the system supports Czech language, but I didn't find the needed definitions for it – the environmental variable definition, keyboard extension and translation file extension.

> Any idea where I can find this info?

>

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117882

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117885: RE: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

2017-07-17T13:09:47Z

Hi Kevin:

Please keep me informed if possible as we have a good number of customers with this issue.

- Thanks,

Kevin

-----Original Message-----

From: Kevin Kunka [mailto:community-noreply@qnx.com]

Sent: Friday, July 14, 2017 10:56 AM

To: general-qnx4 <general-qnx4@community.qnx.com>

Subject: Re: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

SMBfsys is based on SMBv1, so yes, disabling this on the Windows side will prevent a QNX machine from communicating via this mechanism. We are investigating alternative options to address this issue.

_______________________________________________

General

http://community.qnx.com/sf/go/post117879

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117882: Czech language support

2017-07-16T08:12:33Z

According to QNX 4 documentation the system supports Czech language, but I didn't find the needed definitions for it – the environmental variable definition, keyboard extension and translation file extension.

Any idea where I can find this info?

post117880: Re: Dev32.ser MEMIO

2017-07-14T15:21:33Z

Hi Klaus,

Please find attached updated Dev32.ser. Keep in mind that this is an experimental software.

Respectfully,

Oleg

12 июля 2017 г., в 17:41:52, Klaus Pantleon <community-noreply@qnx.com> написал:

> I can make the tests. If you have a Dev32.ser with the code extension from AddiData.

> Of course I can send you one if that will help.

> BR, Klaus

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117869

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117879: Re: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

2017-07-14T14:55:52Z

SMBfsys is based on SMBv1, so yes, disabling this on the Windows side will prevent a QNX machine from communicating via this mechanism. We are investigating alternative options to address this issue.

post117874: Petya Malware concerns wrt SMBfsys talking to SMB software on Windows computer

2017-07-12T19:57:57Z

As you are aware, there is malware that has recently been released called Petya, upon investigation into what is impacted by this malware, it turns out that SMB Ver. 1 on the Windows platform is potentially impacted by this virus. it is recommended that SMB Ver. 1 therefore be shut down.

As you know we have a number of QNX 4 customers out there that are using SMB as the network transport layer to archive data and system back-ups as well as for transferring information between a QNX system and a Windows system. My question is if our customer goes on to the Windows PC and turns off the SMB Ver. 1 feature, will this impact the transfer of data between QNX and the Windows PC. I'm assuming that SMBfsys on the QNX side communicates with an SMB type driver on the Windows side. I'm just not sure if the Windows version of the SMB is what is used with the QNX SMBfys. Also has this concern been raised already.

Thanks in advance ,

Kevin

post117869: Re: Dev32.ser MEMIO

2017-07-12T14:41:52Z

I can make the tests. If you have a Dev32.ser with the code extension from AddiData.

Of course I can send you one if that will help.

BR, Klaus

post117868: Re: Dev32.ser MEMIO

2017-07-12T14:36:59Z

Hi Klaus,

Unfortunately, I can't find any MMIO based serial controllers, so I can't check the driver.

Respectfully,

Oleg

12 июля 2017 г., в 16:43:32, Klaus Pantleon <community-noreply@qnx.com> написал:

> Hi Oleg, any success?

> The vendor punishes me to take the PCIe Cards.

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117867

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117867: Re: Dev32.ser MEMIO

2017-07-12T13:43:32Z

Hi Oleg, any success?

The vendor punishes me to take the PCIe Cards.

post117853: Re: qnx 4 under Microsoft Hyper V

2017-07-06T18:36:20Z

Hi Chaim,

I didn’t run QNX 4 under Hyper-V. But according to my experience in Hyper-V may be troubles with using QNX 4. By my opinion, Hyper-V is very closed virtual environment that supports only Windows-family OSes. Linux and FreeBSD support layer has been developed by Microsoft. I belive that the best virtual solution for QNX are VMware products, but VirtualBox and QEMU/KVM are good too.

Respectfully,

Oleg

6 июля 2017 г., в 17:07, Chaim Filiba <community-noreply@qnx.com> написал:

> can someone tell the QNX4 configuration to use in order runt it under Hyper V?

> under Virtual PC 2007 it runs OK.

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117852

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117852: qnx 4 under Microsoft Hyper V

2017-07-06T14:07:57Z

can someone tell the QNX4 configuration to use in order runt it under Hyper V?

under Virtual PC 2007 it runs OK.

post117830: RE: RE: QNX4.22 and QNX4.22A

2017-06-28T17:26:49Z

Hi Eric:

Thanks for your input. It is appreciated.

- Kevin

-----Original Message-----

From: Eric Johnson [mailto:community-noreply@qnx.com]

Sent: Wednesday, June 28, 2017 11:59 AM

To: general-qnx4 <general-qnx4@community.qnx.com>

Subject: Re: RE: QNX4.22 and QNX4.22A

There should be no problem with 4.22 and 4.22A on the same network. I was around at the time, and also looked at the 4.22A errata sheet out of our archives to make sure there's no mention of a problem in that area.

_______________________________________________

General

http://community.qnx.com/sf/go/post117829

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117829: Re: RE: QNX4.22 and QNX4.22A

2017-06-28T15:58:59Z

There should be no problem with 4.22 and 4.22A on the same network. I was around at the time, and also looked at the 4.22A errata sheet out of our archives to make sure there's no mention of a problem in that area.

post117810: RE: QNX4.22 and QNX4.22A

2017-06-22T13:02:09Z

Thanks Oleg

-kevin

-----Original Message-----

From: Олег Большаков [mailto:community-noreply@qnx.com]

Sent: Thursday, June 22, 2017 3:49 AM

To: general-qnx4@community.qnx.com

Subject: Re: QNX4.22 and QNX4.22A

Hi Kevin,

I guess there can't be quick answer. QNX 4.22 is not supported now. I do not even have QNX 4.22 on my hands. The only current QNX 4.25 is supported. But I guess that QNX 4.22 and QNX 4.22A should be similar and at least backward compatible. QNX 4.22A should be a patch for QNX 4.22.

Respectfully,

Oleg

21 июня 2017 г., в 21:20:38, Kevin Warkentin(deleted) <community-noreply@qnx.com> написал:

> ABB has hundreds of customers still using the old QNX 4 software and we have a question that can probably be answered quickly by a QNX4 person.Can computers running QNX4.22 software run on the same QNX network as another computer running QNX 4.22A ? Are the two versions basically the same?

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117801

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

_______________________________________________

General

http://community.qnx.com/sf/go/post117808

To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117808: Re: QNX4.22 and QNX4.22A

2017-06-22T07:48:37Z

Hi Kevin,

I guess there can't be quick answer. QNX 4.22 is not supported now. I do not even have QNX 4.22 on my hands. The only current QNX 4.25 is supported. But I guess that QNX 4.22 and QNX 4.22A should be similar and at least backward compatible. QNX 4.22A should be a patch for QNX 4.22.

Respectfully,

Oleg

21 июня 2017 г., в 21:20:38, Kevin Warkentin(deleted) <community-noreply@qnx.com> написал:

> ABB has hundreds of customers still using the old QNX 4 software and we have a question that can probably be answered quickly by a QNX4 person.Can computers running QNX4.22 software run on the same QNX network as another computer running QNX 4.22A ? Are the two versions basically the same?

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117801

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117801: QNX4.22 and QNX4.22A

2017-06-21T18:20:38Z

ABB has hundreds of customers still using the old QNX 4 software and we have a question that can probably be answered quickly by a QNX4 person.Can computers running QNX4.22 software run on the same QNX network as another computer running QNX 4.22A ? Are the two versions basically the same?

post117734: Re: Dev32.ser MEMIO

2017-05-12T19:28:24Z

Hi Klaus,

Thanks for your input. I’ll look at this.

Respectfully,

Oleg

12 мая 2017 г., в 16:16, Klaus Pantleon <community-noreply@qnx.com> написал:

> Hello QNX admins.

>

> I want to use a PCIexpress serial card from AddiData to substitute PCI cards.

> But the new cards only support Memory IO access and not a base address any more.

> Therefore the producer extended an older Version of the Dev32.ser and we checked the usability with the new cards and it was working.

> Can you check the attached Dev32.ser patch for the implementation in a newer Dev32.ser?

> I dont want to loose the new feature of Interrupt share ability when I use the already developed update of an older Dev32.ser.

>

> BR, Klaus Pantleon

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117733

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

> <dev.diff>

post117733: Dev32.ser MEMIO

2017-05-12T13:16:10Z

Hello QNX admins.

I want to use a PCIexpress serial card from AddiData to substitute PCI cards.

But the new cards only support Memory IO access and not a base address any more.

Therefore the producer extended an older Version of the Dev32.ser and we checked the usability with the new cards and it was working.

Can you check the attached Dev32.ser patch for the implementation in a newer Dev32.ser?

I dont want to loose the new feature of Interrupt share ability when I use the already developed update of an older Dev32.ser.

BR, Klaus Pantleon

post117728: Re: Request for VME driver on QNX 4.25

2017-05-11T09:38:50Z

Hello Cong,

VME is not supported by QNX 4. So you can develop your own software for your controller.

Respectfully,

Oleg

11 мая 2017 г., в 12:35:43, Cong Pham <community-noreply@qnx.com> написал:

> Uhm..

>

> How can I get VME manager source code to build myself for QNX4?

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117727

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117727: Re: Request for VME driver on QNX 4.25

2017-05-11T09:35:43Z

Uhm..

How can I get VME manager source code to build myself for QNX4?

post117706: Re: Request for VME driver on QNX 4.25

2017-05-04T11:04:18Z

Hi Cong,

VME is not supported by QNX 4. But you can develop driver for your controller by yourself.

Respectfully,

Oleg

4 мая 2017 г., в 13:10:02, Cong Pham <community-noreply@qnx.com> написал:

> Hi everyone,

>

> I have a board with IDT VME universe chip (PCI to VME bridge). I need a VME driver for QNX 4.25.

> I am looking for it from internet, and I found some information for Linux, but nothing found for QNX.

>

> So, if you have any VME driver for QNX 4.25 or source code to build it, please help me.

>

> My email congpx@gmail.com.

>

> Thanks

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117705

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

> <VME2.png>

post117705: Request for VME driver on QNX 4.25

2017-05-04T10:10:02Z

Hi everyone,

I have a board with IDT VME universe chip (PCI to VME bridge). I need a VME driver for QNX 4.25.

I am looking for it from internet, and I found some information for Linux, but nothing found for QNX.

So, if you have any VME driver for QNX 4.25 or source code to build it, please help me.

My email congpx@gmail.com.

Thanks

post117428: Re: virtual circuit close timeout

2017-02-15T13:17:57Z

Hi Oleg,

Unfortunately the way we use 'sin ne' is this:

we have a script which is run periodically by cron, this script is checking system and network health and logs this information for later examination if needed.

This script executes 'sin ne' and if the sin does not end within a timeout, then a signal is sent to it (does not have to be sigint).

Also we found that 'cat' utility also does that and 'wd' watcom debugger too.

And there are probably many other cases.

It is just easy to test it using 'sin ne' and ctrl+c.

Thank you,

stepan hejny

post117427: Re: virtual circuit close timeout

2017-02-15T08:59:46Z

Hi Stepan,

Please find attached the sin utility which blocks SIGINT in case of sin ne. I guess you can use this as a workaround.

Respectfully,

Oleg

9 февр. 2017 г., в 19:42:41, s h <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Yes, as far as i know it happens only when interrupt signal is sent on a process which have virtual circuit in a special state.

>

> stepan hejny

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117408

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117419: Re: Install Problem on HP Proliant ML110

2017-02-13T07:56:56Z

Hi Victor,

I'm glad to hear that you have resolved your issue.

Respectfully,

Oleg

11 февр. 2017 г., в 20:57:29, Victor Gamboa <community-noreply@qnx.com> написал:

> It works! I installed the OS on another machine, install the Proc32 from 01-11-2016, made the OS image and put the HD on the HP machine, and works....

> Greetings Oleg.

> Victor.

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117418

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117418: Re: Install Problem on HP Proliant ML110

2017-02-11T17:57:29Z

It works! I installed the OS on another machine, install the Proc32 from 01-11-2016, made the OS image and put the HD on the HP machine, and works....

Greetings Oleg.

Victor.

post117417: Re: Install Problem on HP Proliant ML110

2017-02-11T00:13:01Z

Hi Oleg, thanks for your help. I am attaching 3 images, the last one is just before the computer resets.

I tried with Legacy Sata and AHCI with the same problem. I really appreciate any help.

Victor.

post117412: Re: Install Problem on HP Proliant ML110

2017-02-10T05:35:18Z

Hi Victor,

What hardware recognition causes the hangout? Can you post here a photo?

Respectfully,

Oleg

10 февр. 2017 г., в 2:22, Victor Gamboa <community-noreply@qnx.com> написал:

> Hi, I tried to install QNX4 on HP Proliant ML110 Server with the Product Suite 2015 but when tried to recognize the hardware, the SO hang out. I tried with SATA and AHCI. I really appreciate any help and thank you in advance for the support.

> Victor Gamboa

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117411

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117411: Install Problem on HP Proliant ML110

2017-02-09T23:22:44Z

Hi, I tried to install QNX4 on HP Proliant ML110 Server with the Product Suite 2015 but when tried to recognize the hardware, the SO hang out. I tried with SATA and AHCI. I really appreciate any help and thank you in advance for the support.

Victor Gamboa

post117408: Re: virtual circuit close timeout

2017-02-09T16:42:41Z

Hi Oleg,

Yes, as far as i know it happens only when interrupt signal is sent on a process which have virtual circuit in a special state.

stepan hejny

post117407: Re: virtual circuit close timeout

2017-02-09T16:28:48Z

Hi Stepan,

As I understand the problem occurs after pressing Ctrl+C. Or does it occur any other way also?

Respectfully,

Oleg

8 февр. 2017 г., в 13:42, s h <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Oh, the example with sin is just to reproduce the problem easily.

> However if this problem is only when breaking sin then sure, we can workaround it.

>

> We have a main and backup system, whatever happens on either one of them must not cause problem for the other. Currently communication between the systems is FLEET. If suitable solution is not found we may have to rewrite the communication to tcp.

>

> Thank you,

> stepan hejny

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117402

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117405: Re: Maximum devices in Dev?

2017-02-09T11:55:23Z

Hi Andy,

I've just checked Dev and it seems to work fine on my system even with "Dev -n10000 &". I also use Proc32 4.25R and Dev32 4.23G. May be the problem is not in Dev. Do you really need 300 devices? Is it possible to run another Dev from command line after the system is booted?

Respectfully,

Oleg

9 февр. 2017 г., в 2:53:52, Andy Rhind <community-noreply@qnx.com> написал:

> Oleg:

>

> Thank you for the reply.

>

> I thought there wasn't an upper limit either. When I do "Dev -n200 &" All is ok, but "Dev -n300 &" appears to lock up and the booting process stops.

>

> Proc32 is 4.25R, Dev32 is 4.23G

>

> Thanks,

> Andy

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117403

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117403: Re: Maximum devices in Dev?

2017-02-08T23:53:52Z

Oleg:

Thank you for the reply.

I thought there wasn't an upper limit either. When I do "Dev -n200 &" All is ok, but "Dev -n300 &" appears to lock up and the booting process stops.

Proc32 is 4.25R, Dev32 is 4.23G

Thanks,

Andy

post117402: Re: virtual circuit close timeout

2017-02-08T10:42:36Z

Hi Oleg,

Oh, the example with sin is just to reproduce the problem easily.

However if this problem is only when breaking sin then sure, we can workaround it.

We have a main and backup system, whatever happens on either one of them must not cause problem for the other. Currently communication between the systems is FLEET. If suitable solution is not found we may have to rewrite the communication to tcp.

Thank you,

stepan hejny

post117401: Re: virtual circuit close timeout

2017-02-08T10:17:11Z

Hi Stepan,

Sorry for the delay with my answer. As I understand correctly, the problem occurs when you press Ctrl+C. Why do you use this combination of keys in this situation when you know that this causes the timeout? Will be solution for you the updated sin which blocks Ctrl+C signal?

Respectfully,

Oleg

30 янв. 2017 г., в 13:26:20, s h <community-noreply@qnx.com> написал:

> Hi Oleg,

>

> Our main problem is that local machine is unable to spawn new processes while this timeout is in effect.

>

> And for solution,

> we understand that there is a lock in kernel which is engaged while process is terminating (in this case virtual circuit).

> Is it possible to relax this lock to keep all the stuff safe and at the same time allow spawning of new processes?

>

> Thank you,

> stepan hejny

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117383

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117399: Re: Maximum devices in Dev?

2017-02-07T11:54:53Z

Hi Andy,

Dev does not have upper limit for maximum number of devices, so theoretically this value is limited by the available RAM.

Respectfully,

Oleg

7 февр. 2017 г., в 3:17:47, Andy Rhind <community-noreply@qnx.com> написал:

> Hi:

>

> Hopefully a simple question. What is the maximum number of devices that can be registered with Dev?

>

> I see the default is 64 and the examples refer to 100, but whats the maximum?

>

> Thanks,

> Andy

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117397

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117397: Maximum devices in Dev?

2017-02-07T00:17:47Z

Hi:

Hopefully a simple question. What is the maximum number of devices that can be registered with Dev?

I see the default is 64 and the examples refer to 100, but whats the maximum?

Thanks,

Andy

post117393: Re: How To Change Process Base Address

2017-02-03T15:32:00Z

Answered my own question - one can change the process base address by passing a custom linker script to the linker using the -T option.

post117392: Re: How To Change Process Base Address

2017-02-03T11:19:06Z

Hi Willard,

What version of QNX do you use? It seems that your question is about QNX Neutrino (or QNX 6) the next version of QNX 4. If so then please ask your question in appropriate discussion board. Thank you for your understanding.

Respectfully,

Oleg

2 февр. 2017 г., в 22:22:46, Willard Williamson <community-noreply@qnx.com> написал:

> Is it possible to change the process base address? For example, a process typically loads at 0x08048000. Is it possible to offset the process base address to something like 0x08049000 and guarantee that it will load at that address every time the process runs?

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117389

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117389: How To Change Process Base Address

2017-02-02T19:22:46Z

Is it possible to change the process base address? For example, a process typically loads at 0x08048000. Is it possible to offset the process base address to something like 0x08049000 and guarantee that it will load at that address every time the process runs?

post117383: Re: virtual circuit close timeout

2017-01-30T10:26:20Z

Hi Oleg,

Our main problem is that local machine is unable to spawn new processes while this timeout is in effect.

And for solution,

we understand that there is a lock in kernel which is engaged while process is terminating (in this case virtual circuit).

Is it possible to relax this lock to keep all the stuff safe and at the same time allow spawning of new processes?

Thank you,

stepan hejny

post117381: Re: virtual circuit close timeout

2017-01-27T14:48:44Z

Hi Stepan,

We’ve reproduced your issue. What is a main problem for you in this situation? Is it behaviour of 'sin ne’ or an effect of pressing of Ctr+C? How do you see a solution for the issue? Keep in mind that QNX FLEET extends the QNX IPC to the network of tightly coupled QNX microkernels. So I guess the hardware problem in this case may affect on whole QNX network.

Respectfully,

Oleg

23 янв. 2017 г., в 20:15, s h <community-noreply@qnx.com> написал:

> Hi,

>

> I just tried it on virtual machines and at first i was not able to reproduce it as well.

> I did 'slay -n2 -sstop Fsys.eide' and 'sin ne' did not block.

>

> So i tried to block any process on remote Fsys, e.g. 'ls //2'.

> The 'ls' blocked now and then i tried 'sin ne' and it blocked and when i tried to ctrl+c the 'sin ne' it introduced the described problem.

>

> stepan hejny

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117370

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117375: Re: virtual circuit close timeout

2017-01-24T08:58:47Z

Hi Stepan,

I'll try with ls utility.

Respectfully,

Oleg

23 янв. 2017 г., в 20:15:46, s h <community-noreply@qnx.com> написал:

> Hi,

>

> I just tried it on virtual machines and at first i was not able to reproduce it as well.

> I did 'slay -n2 -sstop Fsys.eide' and 'sin ne' did not block.

>

> So i tried to block any process on remote Fsys, e.g. 'ls //2'.

> The 'ls' blocked now and then i tried 'sin ne' and it blocked and when i tried to ctrl+c the 'sin ne' it introduced the described problem.

>

> stepan hejny

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117370

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117370: Re: virtual circuit close timeout

2017-01-23T17:15:46Z

Hi,

I just tried it on virtual machines and at first i was not able to reproduce it as well.

I did 'slay -n2 -sstop Fsys.eide' and 'sin ne' did not block.

So i tried to block any process on remote Fsys, e.g. 'ls //2'.

The 'ls' blocked now and then i tried 'sin ne' and it blocked and when i tried to ctrl+c the 'sin ne' it introduced the described problem.

stepan hejny

post117359: Re: virtual circuit close timeout

2017-01-20T22:10:36Z

Hi Stepan,

I can’t reproduce your issue. I’m using two virtual PC which are connected by FLEET. At one machine I execute slay -s stop Fsys.atapi, then on second machine I run sin ne. I don’t see timeout.

Can you send me the following output?

sin ver

sin ar

sin ir

sin in

show_pci -vvv

Do you reproduce this issue on specific hardware or on different configurations?

Respectfully,

Oleg

19 янв. 2017 г., в 15:17, s h <community-noreply@qnx.com> написал:

> Hi,

>

> We have encountered a problem with timeout when a virtual circuit is being closed.

>

> There are 2 machines connected using FLEET.

>

> On one machine there was a hardware problem and Fsys.atapi crashed.

>

> At some later time on the second machine 'sin ne' is executed.

> Process sin becomes indefinitely blocked on virtual circuit to Fsys on other machine.

> Then when interrupt signal (ctrl+c) is sent to the sin process, the Proc is closing the virtual circuit with 1 minute timeout.

>

> During this timeout the second machine is unable to create or terminate processes which is the real problem.

>

> We are able to reproduce the problem by stopping Fsys driver on the machine using 'slay -sstop Fsys.atapi'.

> One way to induce the create/terminate process timeout is the 'sin ne' but there are other commands which can induce it.

>

> Bottom line is that a problem on one machine can introduce a "bigger" problem on another machine.

> Any advice?

>

> Thanks,

> stepan hejny

>

>

>

>

> _______________________________________________

>

> General

> http://community.qnx.com/sf/go/post117350

> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com

post117350: virtual circuit close timeout

2017-01-19T12:17:30Z

Hi,

We have encountered a problem with timeout when a virtual circuit is being closed.

There are 2 machines connected using FLEET.

On one machine there was a hardware problem and Fsys.atapi crashed.

At some later time on the second machine 'sin ne' is executed.

Process sin becomes indefinitely blocked on virtual circuit to Fsys on other machine.

Then when interrupt signal (ctrl+c) is sent to the sin process, the Proc is closing the virtual circuit with 1 minute timeout.

During this timeout the second machine is unable to create or terminate processes which is the real problem.

We are able to reproduce the problem by stopping Fsys driver on the machine using 'slay -sstop Fsys.atapi'.

One way to induce the create/terminate process timeout is the 'sin ne' but there are other commands which can induce it.

Bottom line is that a problem on one machine can introduce a "bigger" problem on another machine.

Any advice?

Thanks,

stepan hejny

post117304: Re: realtek 8169 second ethernet port failure to init

2017-01-04T18:46:42Z

The rtl8169 driver hasn¹t been updated in years, so maybe it needs an

update. I don¹t have the time to do it now, but if you want to contact

your QNX sales rep and see if he can schedule something. I would also need

the hardware, so that I could verify the driver.

On 2017-01-04, 1:36 PM, "Jesus Gomez" <community-noreply@qnx.com> wrote:

>Unfortunately I do not have another system. This is my test system before

>I buy a lot from OEM.

>

>DO you need any other diags.

>

>They tell me, they use the 8111E realtek chipset.

>

>http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PF

>id=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

>

>Thanks for your interest, regards

>

>Jesus Gomez

>

>

>

>

>_______________________________________________

>

>General

>http://community.qnx.com/sf/go/post117302

>To cancel your subscription to this discussion, please e-mail

>general-qnx4-unsubscribe@community.qnx.com

post117303: Re: realtek 8169 second ethernet port failure to init

2017-01-04T18:40:41Z

Just found out the Jun 29th, 2009 Net.rtl8169 behaves similarly, only works for Port 1, but not for Port 2.

Thanks,

Jesus Gomez

post117302: Re: realtek 8169 second ethernet port failure to init

2017-01-04T18:36:57Z

Unfortunately I do not have another system. This is my test system before I buy a lot from OEM.

DO you need any other diags.

They tell me, they use the 8111E realtek chipset.

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

Thanks for your interest, regards

Jesus Gomez

post117301: Re: realtek 8169 second ethernet port failure to init

2017-01-04T16:23:53Z

This is really weird! From the pci output that you posted, it appears that

you have 2 identical RTL8169 chips on your system, but they both give

different tcrval outputs. The one is 0x80040002 and the other is

0x2F200000. Do you have more than one of these systems? If so, do they all

give the same result?

Thanks, Hugh.

On 2017-01-04, 11:12 AM, "Jesus Gomez" <community-noreply@qnx.com> wrote:

> As you asked, and I also included for -I0 so you can see the differences

>With -vvv

>

>Thanks again,

>

>Jesus Gomez

>

>

>

>

>_______________________________________________

>

>General

>http://community.qnx.com/sf/go/post117300

>To cancel your subscription to this discussion, please e-mail

>general-qnx4-unsubscribe@community.qnx.com

post117300: Re: realtek 8169 second ethernet port failure to init

2017-01-04T16:12:04Z

As you asked, and I also included for -I0 so you can see the differences With -vvv

Thanks again,

Jesus Gomez

post117299: Re: realtek 8169 second ethernet port failure to init

2017-01-03T13:21:15Z

Hello Jesus,

If you slay Net and Net.rtl8169, and then run ³Net &² followed by

³Net.rtl8169 -I1 &², does the second interface come up? It is strange that

the tcrval for the second interface is not the same as the first interface.

Thanks, Hugh.

On 2017-01-02, 6:59 PM, "Jesus Gomez" <community-noreply@qnx.com> wrote:

>Hello Hugh,

>

>I'm running the latest Oct 30 2014 release of Net.rtl8169 and Net.

>

>Photon runs ok and network port 1 runs Ok as well, so far with the TCP/IP

>stack.

>

>System has a VGA and VDI port, but we are using the VGA port only. We

>have made BIOS change for only VGA mode.(IGD and CRT settings). USB

>keyboard and mouse works.

>

>However system complaints at initialization before the graphics

>environment loads, I have traced back to have a minimal system running

>with Net and Net.rtl8169, port 2 (PCI-1) always fails to initialize.

>System indicates is a RTL8111E-VB-CG x 2 gigabit ethernet chipset.

>

>I'm including screenshots of the system.

>

>Could you help us please, this is a prototype system for production.

>

>Regards,

>

>Jesus Gomez

>AMI GE

>

>

>

>

>_______________________________________________

>

>General

>http://community.qnx.com/sf/go/post117298

>To cancel your subscription to this discussion, please e-mail

>general-qnx4-unsubscribe@community.qnx.com