Hi again. That with the network appeared once more. Here are they both: Probing for an unused private subnet (this can take some time). The subnet 172.16.14.0/255.255.255.0 appears to be unused. Press enter to display the DHCP server copyright information. Creating a host-only network on vmnet1. (this is required to share the host's filesystem). Configuring a host-only network for vmnet1. Do you want this script to probe for an unused private subnet? (yes/no/help) [yes] yes Probing for an unused private subnet (this can take some time). The subnet 172.16.150.0/255.255.255.0 appears to be unused. This system appears to have a CIFS/SMB server (Samba) configured for normal use. If this server is intended to run, you need to make sure that it will not conflict with the Samba server setup on the private network (the one that we use to share the host's filesystem). Please check your /etc/samba/smb.conf file so that: . The "interfaces" line does not contain "172.16.150.1/255.255.255.0" . There is a "socket address" line that contains only your real host IP address Hit enter to continue. Can you tell me what to do ? -- Med venlig hilsen/Best regards/vy73 de oz4kk Erik Jakobsen - erik@urbakken.dk Powered by SuSE 7.3 Linux
On Wed, 2001-12-19 at 11:01, Erik Jakobsen wrote:
Hi again.
That with the network appeared once more. Here are they both:
Probing for an unused private subnet (this can take some time).
The subnet 172.16.14.0/255.255.255.0 appears to be unused.
Press enter to display the DHCP server copyright information.
Creating a host-only network on vmnet1. (this is required to share the host's filesystem).
Configuring a host-only network for vmnet1.
Do you want this script to probe for an unused private subnet? (yes/no/help) [yes] yes
Probing for an unused private subnet (this can take some time).
The subnet 172.16.150.0/255.255.255.0 appears to be unused.
This system appears to have a CIFS/SMB server (Samba) configured for normal use. If this server is intended to run, you need to make sure that it will not conflict with the Samba server setup on the private network (the one that we use to share the host's filesystem). Please check your /etc/samba/smb.conf file so that:
. The "interfaces" line does not contain "172.16.150.1/255.255.255.0" . There is a "socket address" line that contains only your real host IP address
Hit enter to continue.
Can you tell me what to do ? --
Hi Erik, VMWare will set up it's own SAMBA server so that Windoze clients installed in VMWare can access you Host's local drives. If you check in the file mentioned (/etc/samba/smb.conf) like the message say and hit enter. You normally should not have a problem as long as The "interfaces" line does not contain "172.16.150.1/255.255.255.0" and There is a "socket address" line that contains only your real host IP address. If you don't have SAMBA set up on your host, don't worry about it. I have been using VMWare for over a year and I have never had problems with the default settings that the config script suggest. If you do have a SAMBA server configured on your system, you can select 'no' when the script asks if you want the clients to access your host's file systems. Hope this helps -- Andre Truter Software Engineer <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
Hi Erik,
Hi Andre.
VMWare will set up it's own SAMBA server so that Windoze clients installed in VMWare can access you Host's local drives.
Ok fine.
If you check in the file mentioned (/etc/samba/smb.conf) like the message say and hit enter.
Ok.
You normally should not have a problem as long as The "interfaces" line does not contain "172.16.150.1/255.255.255.0" and There is a "socket address" line that contains only your real host IP address.
Such it is.
If you don't have SAMBA set up on your host, don't worry about it.
OK.
I have been using VMWare for over a year and I have never had problems with the default settings that the config script suggest.
Fine.
If you do have a SAMBA server configured on your system, you can select 'no' when the script asks if you want the clients to access your host's file systems.
Very good, and thanks for the info. Later today I installed Windows XP in my Workstation. Every thing but min LJ1100A does work ok. Once I had it up on another harddisk there were no problems at all. I do have the latest CD-Rom for my LJ1100A and it supports XP. I have the following set in my /etc/group file for my "lp": lp:x:7:erik In the vmware I have switched off the bidirectional in the LPT1 setup. Then there are no errors at boot up. If I set the bidirectional to on, following info comes up: "The bidirectional virtual device LPT1 is using the old-style unidirectional host device /dev/lp0. You must either turn off bidirectional mode for LPT1 in the configuration editor, or change its path to a parport-style device )probably /dev/parport0) Device parallel0 will start disconnected" At the time when the printer worked, it was set to /dev/lp0. Of course there is something not as it should be, but I cannot think what. Do you have any ideas, or if anybody else reads this, and have experience with the problem I have, then please come on with what you may help me with. I write to SLE because I have had no feedback asking the same on the vmware news group.
Hope this helps
Thank you Andre. -- Med venlig hilsen/Best regards/vy73 de oz4kk Erik Jakobsen - erik@urbakken.dk Powered by SuSE 7.3 Linux
Hi Erik, On Wed, 2001-12-19 at 21:25, Erik Jakobsen wrote:
Later today I installed Windows XP in my Workstation. Every thing but min LJ1100A does work ok.
Once I had it up on another harddisk there were no problems at all.
I do have the latest CD-Rom for my LJ1100A and it supports XP.
I have the following set in my /etc/group file for my "lp":
lp:x:7:erik
In the vmware I have switched off the bidirectional in the LPT1 setup.
Then there are no errors at boot up.
If I set the bidirectional to on, following info comes up:
"The bidirectional virtual device LPT1 is using the old-style unidirectional host device /dev/lp0. You must either turn off bidirectional mode for LPT1 in the configuration editor, or change its path to a parport-style device )probably /dev/parport0) Device parallel0 will start disconnected"
At the time when the printer worked, it was set to /dev/lp0.
Of course there is something not as it should be, but I cannot think what.
Do you have any ideas, or if anybody else reads this, and have experience with the problem I have, then please come on with what you may help me with.
I write to SLE because I have had no feedback asking the same on the vmware news group.
I have VMWare running on a RedHat box, but I assume it should work the same on SuSE. You need the parport and parport_pc modules to be loaded. I wrote my own init script that is called during system initialisation to load the modules for me. Here it is: ---------------- #!/bin/sh # # Source functions . /etc/init.d/functions alias=`egrep -s "^alias[[:space:]]+parport_lowlevel[[:space:]]+" /etc/modules.conf | awk '{ print $3 }'` if [ -n "$alias" -a "$alias" != "off" ] ; then action "Initializing ($alias): " modprobe $alias else echo "parport_lowlevel not in modules.conf" fi # this is all. # I have to add error detection also ... later ------------ And I added the following line to /etc/modules.conf ----<snip>---- alias parport_lowlevel parport_pc ----<snip>---- Unfortunately I cannot help you much with setting up this script in SuSE, as I have only been using SuSE since Monday (3 days) :-) I do see that there is an parport entry in my SuSE box's /etc/modules.conf. Maybe someone else can help you to get the parport modules to load on boot. But to check if it helps now, you should be able to do: modprobe parport_pc now to get the modules loaded. Do 'lsmod' to see if the modules are running. Then you need to set your parallel port as /dev/parport0 in the VMWare settings. Hope this helps -- Andre Truter Software Engineer <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
On Wednesday 19 December 2001 20:53, Andre Truter wrote:
Hi Erik,
Hi Andre.
I have VMWare running on a RedHat box, but I assume it should work the same on SuSE.
You need the parport and parport_pc modules to be loaded.
I wrote my own init script that is called during system initialisation to load the modules for me.
Thank you for your script, but have a look here. It seems I have both parport and parport_pc: shamrock:~ # lsmod parport_pc 19280 2 parport 22240 2 [vmppuser lp ppa parport_pc] shamrock:~ # And permissions: shamrock:~ # ls -l /dev/lp0 crw-rw-rw- 1 root lp 6, 0 Sep 24 03:54 /dev/lp0 shamrock:~ # ls -l /dev/parport0 crw-rw---- 1 root root 99, 0 Sep 24 03:55 /dev/parport0 shamrock:~ # I am not quite sure what permission parport0 should have. Is it the same as lp0 ??. I ask as if I have my path in vmware set to /dev/parport0, following comes up: "Can't open /devparport0: Permission denied. Device parallel0 will start disconnected"
Unfortunately I cannot help you much with setting up this script in SuSE, as I have only been using SuSE since Monday (3 days) :-)
I do see that there is an parport entry in my SuSE box's /etc/modules.conf.
Maybe someone else can help you to get the parport modules to load on boot.
But to check if it helps now, you should be able to do: modprobe parport_pc now to get the modules loaded.
Do 'lsmod' to see if the modules are running.
Then you need to set your parallel port as /dev/parport0 in the VMWare settings.
Hope this helps
I also went into /dev: shamrock:/dev # ls -l ls: ptyr0: Permission denied ls: ptyr1: Permission denied ls: ptyr2: Permission denied ls: ptyr3: Permission denied ls: ptyr4: Permission denied ls: ptyr5: Permission denied ls: ptyr6: Permission denied ls: ptyr7: Permission denied ls: ptyr8: Permission denied shamrock:/dev # Normally I can execute the ls -l here, and can also do it with Midnight Commander, but that has also been closed. I can do a ls -l /dev/lp0 as you can see above. What is causing the above ??. Thank you for your help. And yes maybe also other can help. I invite other to help me. Thank you !!- -- Med venlig hilsen/Best regards/vy73 de oz4kk Erik Jakobsen - erik@urbakken.dk Powered by SuSE 7.3 Linux
On Thu, 2001-12-20 at 08:17, Erik Jakobsen wrote:
Hi Erik
Thank you for your script, but have a look here. It seems I have both parport and parport_pc:
shamrock:~ # lsmod parport_pc 19280 2 parport 22240 2 [vmppuser lp ppa parport_pc] shamrock:~ #
And permissions:
shamrock:~ # ls -l /dev/lp0 crw-rw-rw- 1 root lp 6, 0 Sep 24 03:54 /dev/lp0 shamrock:~ # ls -l /dev/parport0 crw-rw---- 1 root root 99, 0 Sep 24 03:55 /dev/parport0 shamrock:~ #
I am not quite sure what permission parport0 should have. Is it the same as lp0 ??.
Yes, I think you just need to change the group to lp. On my machine it is as follows: [root@obelix etc]# ll /dev/parport0 crw-rw---- 1 root lp 99, 0 Aug 30 22:30 /dev/parport0
I also went into /dev:
shamrock:/dev # ls -l ls: ptyr0: Permission denied ls: ptyr1: Permission denied ls: ptyr2: Permission denied ls: ptyr3: Permission denied ls: ptyr4: Permission denied ls: ptyr5: Permission denied ls: ptyr6: Permission denied ls: ptyr7: Permission denied ls: ptyr8: Permission denied
shamrock:/dev #
Normally I can execute the ls -l here, and can also do it with Midnight Commander, but that has also been closed. I can do a ls -l /dev/lp0 as you can see above.
What is causing the above ??.
Unfortunately I don't know this. It might have something to do with security settings. Do you do the ls as root or a normal user? I have seen that after my upgrade from RH7.0 to 7.1, normal uses were not given permission on certain tty's Regards Andre -- Andre Truter Software Engineer <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
participants (2)
-
Andre Truter
-
Erik Jakobsen