Using PCMCIA IDE Flash with qnx4?

Shashank <sbalijepalli@precitech.com> wrote:

I’ve used SMBFsys to mount a windows folder to my QNX machine and copied
files to it. However, our customers are not very Computer savvy and prefer
having a windows interface to copy large files from their Windows server to
their QNX machine. Some of our customers have large files (upto 1.5GB in
size) residing on their windows computer that need to be copied to their QNX
computers.

Does ICA hog up resources and do you know if it has any limitations?

I’ve used ICA a fair bit on my QNX4 desktop. It seemed to work fairly
well, but it doesn’t sound like it matches what you want.

You talk about the users being at a Windows box, and wanting to copies
files to the QNX box. ICA does not do this. ICA allows a user to sit
at a QNX box, and create a remote UI to a Windows box, that is, to
essentially have all the graphics input and output from a windows box
directed to a QNX box (through the ICA environment). Now, part of the
possible configuration for it is that some parts of the QNX box can
be visible as “drives” in the ICA session – but they are only visible
within the ICA session – they are not available to someone sitting at
the Windows box. And, this takes a fair bit of configuration. As far
as system load, I don’t know what the load is like on the Windows box
running the server, but the load on the QNX box is not too bad. I run
it fairly well on an old, slow, desktop (64M RAM, 133MHz Pentium, I
think) machine.

But, as I said, I don’t think it will do what you want. I think running
Samba on your QNX box, and then mounting that under the Windows boxes
as a Windows share would be the best way to match what you’re trying
to do.

-David

Thanks
Shashank



“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:d81nln$59m$> 4@inn.qnx.com> …
Shashank <> sbalijepalli@precitech.com> > wrote:

I have a Windows 2000 Server that has the Citrix ICA server installed
on
it. I am thikning of installing the Citrix ICA client for QNX 4.2.

Can I then use this software to copy files to and from my Windows
server?
And are there any limitations to this?

I guess you could use ICA for copy files between QNX and Windows, but
really it is more intended for creating a Windows UI session under QNX.

I apprecaite your suggestions.

I’d suggest, instead, using Samba (now called CIFS). This will allow
you to mount a windows “share” under a QNX machine.

A set of commands something like:

#!/bin/sh
/bin/SMBfsys &
sleep 2
/usr/bin/user_smb windows_userid windows_password
/bin/mount_smb “//WindowMachine/WindowsDirectory” /qnx/directory

Then “ls /qnx/directory” will show the contents of the windows directory,
and you can copy files to/from the windows box using normal cp type
commands under QNX.

If you want to “share” your QNX filesystem with a Windows box, you’d
either want a NFS client for Windows, or Samba for QNX. I’ve not
setup Samba, but there seem to be a port of it available at:
ftp.qnx.com:/usr/free/qnx4/tcpip/utils/samba-qnxbin-2.0.4b.tgz

I don’t know how out of date, protocol wise, that will be.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com


David Gibbs
QNX Training Services
dagibbs@qnx.com

Thanks for your reply.
In our case the user will be at the QNX box itself and not at the Windows
box.

If parts of the QNX box can be made visible as “drives”, then can’t a file
resident on Windows 2000 be copied to one of the visible QNX drives.

Shashank









“David Gibbs” <dagibbs@qnx.com> wrote in message
news:d82cfh$kbt$1@inn.qnx.com

Shashank <> sbalijepalli@precitech.com> > wrote:

I’ve used SMBFsys to mount a windows folder to my QNX machine and copied
files to it. However, our customers are not very Computer savvy and
prefer
having a windows interface to copy large files from their Windows server
to
their QNX machine. Some of our customers have large files (upto 1.5GB in
size) residing on their windows computer that need to be copied to their
QNX
computers.

Does ICA hog up resources and do you know if it has any limitations?

I’ve used ICA a fair bit on my QNX4 desktop. It seemed to work fairly
well, but it doesn’t sound like it matches what you want.

You talk about the users being at a Windows box, and wanting to copies
files to the QNX box. ICA does not do this. ICA allows a user to sit
at a QNX box, and create a remote UI to a Windows box, that is, to
essentially have all the graphics input and output from a windows box
directed to a QNX box (through the ICA environment). Now, part of the
possible configuration for it is that some parts of the QNX box can
be visible as “drives” in the ICA session – but they are only visible
within the ICA session – they are not available to someone sitting at
the Windows box. And, this takes a fair bit of configuration. As far
as system load, I don’t know what the load is like on the Windows box
running the server, but the load on the QNX box is not too bad. I run
it fairly well on an old, slow, desktop (64M RAM, 133MHz Pentium, I
think) machine.

But, as I said, I don’t think it will do what you want. I think running
Samba on your QNX box, and then mounting that under the Windows boxes
as a Windows share would be the best way to match what you’re trying
to do.

-David

Thanks
Shashank




“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:d81nln$59m$> 4@inn.qnx.com> …
Shashank <> sbalijepalli@precitech.com> > wrote:

I have a Windows 2000 Server that has the Citrix ICA server
installed
on
it. I am thikning of installing the Citrix ICA client for QNX 4.2.

Can I then use this software to copy files to and from my Windows
server?
And are there any limitations to this?

I guess you could use ICA for copy files between QNX and Windows, but
really it is more intended for creating a Windows UI session under QNX.

I apprecaite your suggestions.

I’d suggest, instead, using Samba (now called CIFS). This will allow
you to mount a windows “share” under a QNX machine.

A set of commands something like:

#!/bin/sh
/bin/SMBfsys &
sleep 2
/usr/bin/user_smb windows_userid windows_password
/bin/mount_smb “//WindowMachine/WindowsDirectory” /qnx/directory

Then “ls /qnx/directory” will show the contents of the windows
directory,
and you can copy files to/from the windows box using normal cp type
commands under QNX.

If you want to “share” your QNX filesystem with a Windows box, you’d
either want a NFS client for Windows, or Samba for QNX. I’ve not
setup Samba, but there seem to be a port of it available at:
ftp.qnx.com:/usr/free/qnx4/tcpip/utils/samba-qnxbin-2.0.4b.tgz

I don’t know how out of date, protocol wise, that will be.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com


\

David Gibbs
QNX Training Services
dagibbs@qnx.com

Shashank <sbalijepalli@precitech.com> wrote:

Thanks for your reply.
In our case the user will be at the QNX box itself and not at the Windows
box.

If parts of the QNX box can be made visible as “drives”, then can’t a file
resident on Windows 2000 be copied to one of the visible QNX drives.

Yes, that should be doable. In fact, my ICA setup has my QNX home
directory, and the / for my QNX machine visible as drives when I’m
using ICA. I just have no clue how I set that up. (I set it up
a few years ago.)

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

I setup my QNX computer and installed the citrix ICA client ver. 1.0 on it.
When I try to connect to the ICA server running on Windows 2000, it gives me
an “E_SERVER_CONNECTION_FAILED” with an error code 49. I contacted Citrix
technical support and they told me that that means I am not running the
latest version of the ICA client.

has anybody come across this error before?

Thanks
Shashank




“David Gibbs” <dagibbs@qnx.com> wrote in message
news:d84a7j$3me$1@inn.qnx.com

Shashank <> sbalijepalli@precitech.com> > wrote:

Thanks for your reply.
In our case the user will be at the QNX box itself and not at the
Windows
box.

If parts of the QNX box can be made visible as “drives”, then can’t a
file
resident on Windows 2000 be copied to one of the visible QNX drives.

Yes, that should be doable. In fact, my ICA setup has my QNX home
directory, and the / for my QNX machine visible as drives when I’m
using ICA. I just have no clue how I set that up. (I set it up
a few years ago.)

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

On Sun, 24 Apr 2005 05:41:03 +0400, Mario Charest postmaster@127.0.0.1
wrote:

There is no _vbprintf. There are version available on the net. Monday I
can email you a copy that I use for QNX4.
I could not find a clean way to integrate any foreign implementation of

v[s]nprintf() into the tool-chain…
So, I ended up with hacking the /usr/include/stdio.h slightly.

After the descriptions of _bprintf() and _vbprintf() I added (as Rob has
advised on Fri, 18 Jan 2002 00:57:16 +0300, Rob <rob@spamyouself.com>):
#define snprintf _bprintf
#define vsnprintf _vbprintf

Seems this works OK, I’ve checked it with zlib v1.23 (the security fix!) -
it’s ./configure now discovers and uses vsnprintf(), all tests pass.

:slight_smile:

Tony.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 01 Sep 2005 17:42:56 +0200, Jacek Rudnicki
<jacek.rudnicki@quantum.com.pl> wrote:

Hi Alex,

Some time ago I had a chance to test that chipset.
As I remember it was Realtek 8100C.

The Net.rtl driver easily handled it and the ‘show_pci’
command showed it Device ID as: 8139h.

Thanks Jacek, appreciated.

On Thu, 01 Sep 2005 14:38:44 +0200, Hugh Brown <hsbrown@qnx.com> wrote:

Hi Alex,
This chip is supposedly 8139 compatible, but we have not been able to
test
it with our driver

Hugh
thanks-I will post confirmation here soon!

\

Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/