Jump to content

john_gallow

Member
  • Posts

    12
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Slovakia

Posts posted by john_gallow

  1. DNSClient is important when your computer is part od Active Directory domain.

    In cooperation DNS <-> Active Driectory there used "dynamic" DNS items, ie. computer starts and Active Directory creates new DNS items for it.

    John

  2. In general:

    (Let's assume C++ :) )

    In general: The simple case is when code is written cleanly by ANSI standard (ANSI C, or standard C++).

    With such code should not be problems to take it and create project in MS Visual Studio or Metrowerks Code Warior (for Mac) or any devel tool for anu other OS.

    If it will contain some system-specific functions, you must to create superseeding functions in devel environments for other OS and this is begin of "rewriting".

    Problem is that konqueror uses graphical output that is mean it cannot be written in clean ANSI C,C++. My assumption is that it contains some part which we can to name: "core of application" - this is probably easy to port - this part should contain small amount of system-specific functions and then this part of code must be linked with some GUI library which is responsible for displaying buttons, trees and other GUI items...

    You must to determine what GUI interface (what GUI library) is used and then to find if there exist this GUI library for other systems. For example Gimp (application for creating pictures - it is available on Linux and also on Windows - it uses GTK++ I think and for this reason on Windows must be also with it installed GTK environment).

    You must also to find layer (interface) konqueror "core" uses on lower side. For example this code reads content of directory - to display it in konqueror output. If it uses for this purpose C Run-Time library then it is simpler case because it is less work with porting that if it uses Linux-specific functions for it.

    To be more exact it is needed to study konqueror code and make deep analyse.

    John

  3. Why do you need to have studio's PCs completely blind to the rest of network ?

    If you dont want to have access to them from rest of network, it can be solved by

    user accounts with access rights, you dont need to disconnect them.

    Wired vs. wireless:

    I ment in previous post that it should be better to have it on cable only for speed.

    I dont see any other reason, only speed, because cable network can be about Gigabit,

    and wireless the most 54Mbit (by type of your your Linksys Wet 54G).

    If you connect backup drive directly to router through cable, it will have no effect,

    because also in this case every computer must to go through wireless way to backup it's data.

    But it does not need to be bad if you for example will to backup every day 10 Mega of data.

    But if you will backup for example 4GB of music, on 22Mbit (ideal speed) it will take about 24 minutes

    on wireless. But mostly parctical speed is less than 22Mbit - depending on antenna placement, material of your house, etc...

    so for example if your practical wireless speed will be only 11Mbit, it take time 48 minutes.

    That is reason why I write about connecting backup drive directly to one of PCs which will have the most data for backuping in your network.

    John

  4. Computer choses network interface for sending IP packets to target by it's routing table.

    Every your hardwired computer has in it's routing table two routes:

    1. Route to wireless subnet 12.168.1.x

    2. Route to cable subnet 192.168.2.x

    This items in routing table are created automatically when network interface starts.

    So dont worry, it choses right route.

    For example:

    your hardwired computer has on the cable interface IP: 192.168.2.1, and the second computer has IP on cable interface: 192.168.1.2

    and

    on wireless interface first has IP: 192.168.1.53 , and the second has wireless IP: 192.168.1.54

    When you try ping 192.168.2.2 from the first computer, it choses cable interface by it's route table, because it knows that it can to connect to subnet 192.168.2.0/255.255.255.0 through cable interface.

    If you ping from the same computer to 192.168.1.54, it choses wireless interface.

    You can verify these pings and you will see in output that pings through wireless are much more slow.

    John

  5. If you are on one of hardwired computers

    and you need to connect to it's hardwired neighbour,

    use it's IP from subnet 192.168.2.x (like I described above).

    If you are on rest of network and you need to connect

    to one of hardwired computers then use

    it's wireless IP from subnet 192.168.1.x .

    Thus you dont need to physically connect/disconnect cable.

    WET54G:

    You have most of backuped data on wireless part of network

    (not two hardwired computers), it's ok,

    but if you mostly will backup data from hardwired computers,

    it can be more quicker to have cable connection to backup device.

    Regards !

    :-)

    John

  6. Yes it is possible to assign also on cable network cards IPs from the same subnet's like you have on wireless, but it leads to complications and you must manually adjust route table to make it functional,

    because if you have not set it correctly then Windows can to use wireless way instead of cable way.

    The more simple way is:

    On wireless interfaces of both hardwired computers let 192.168.1.x/255.255.255.0 adresses with default gateway equal to internal IP of your modem.

    On cable network cards assign different subnet, for example 192.168.2.1/255.255.255.0 and 192.168.2.2/255.255.255.0

    for using cable connection on hardwired computers use IP from this subnet.

    Dont add default gateway in cable network cards.

    Default gateway leave only on wireless interfaces of hardwired computers.

    It should work.

    John

  7. Surely it's possible, but I can provide to you only partial info, because never I did driver installation by this way

    inly once and I had prepared some *.reg files for importing into registry - not prepared by me.

    What kind of driver do you want to install manually ? (graphics, network...)

    Kind of driver you want to install is described by "class ID", it is GUID for some type of drivers,

    so first you must to find your class ID.

    Next in registry you can to find:

    HKLM\CurrentControlSet\Control\Class

    and info about your your driver info will be stored under your "class ID" key.

    Manual adding driver info here assumes that you very good know what you are doing !

    Second place where can be info about your driver is:

    HKLM\CurrentControlSet\Services

    Here must be added key with name of your *.sys driver-based service (*.exe services has also keys here)

    But this info is not complete, take it only like inspiration what other info you must to find.

    If I would be in your role I would to try install this driver by normal way and sniff registry changes by regmon utility,

    and with help of captured registry changes I will try to create *.reg files for importing.

    Creating of *.reg files can be simpler if you look into *.inf file for your driver installation.

    There are registry keys and values which must be added into registry in *.inf file.

    John

×
×
  • Create New...