jump to navigation

ACCPAC 6 “Missing system password file” July 22, 2008

Posted by Cowboy in Uncategorized.
Tags:
add a comment

the system password is in SYPRSC.SYS.  It resides in \ASP.

All hidden files should be copied, with care made to get the ??PRSC.* files in the data
directory(ies).  DOS COPY or XCOPY work fine, once the hidden attributes are turned
off, ATTRIB *.* -h.

You should still get a copy of SYSTEMPW.EXE from WSM disk  1 to
set or change the system password in the future.

Configuring opportunistic locking in Windows July 21, 2008

Posted by Cowboy in Uncategorized.
add a comment

function loadTOCNode(){}

Article ID : 296264
Last Review : December 3, 2007
Revision : 9.5
This article was previously published under Q296264

SUMMARY

loadTOCNode(1, ’summary’);

By default, opportunistic locking is enabled for server message block (SMB) clients that run one of the Windows operating systems that is listed in the “Applies to” section. Opportunistic locking lets clients lock files and locally cache information without the risk of another user changing the file. This increases performance for many file operations but may decrease performance in other operations because the server that grants the opportunistic lock must manage the breaking of that lock when another user requests access to the file.

Notes for Windows Vista

The opportunistic locking registry keys are valid only for traditional SMB (SMB1). You cannot turn off opportunistic locking for SMB2. SMB2 was introduced in Windows Vista to enable faster communication between computer that are running Windows Vista and Windows Server 2008.
If you disable opportunistic locking, the offline files feature in Windows Vista fails.

MORE INFORMATION

loadTOCNode(1, ‘moreinformation’);

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows

The location of the client registry entry for opportunistic locking has changed from the location in Microsoft Windows NT. In later versions of Windows, you can disable opportunistic locking by setting the following registry entry to 1:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
OplocksDisabled REG_DWORD 0 or 1
Default: 0 (not disabled)

Note The OplocksDisabled entry configures Windows clients to request or not to request opportunistic locks on a remote file.

You can also deny the granting of opportunistic locks by setting the following registry entry to 0:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
EnableOplocks REG_DWORD 0 or 1
Default: 1 (enabled)

Note The EnableOplocks entry configures Windows-based servers to allow or to deny opportunistic locks on local files. These servers include workstations that share files.

In addition, you can use the following values to tune opportunistic locking for Windows-based computers that have granted opportunistic locks.

The following value specifies the minimum link throughput that the server allows before it disables raw and opportunistic locks for this connection:

MinLinkThroughput REG_DWORD 0 to infinite bytes per second
Default: 0

The following value specifies the maximum time that is allowed for a link delay. If delays exceed this number, the server disables raw I/O and opportunistic locking for this connection.

MaxLinkDelay REG_DWORD 0 to 100,000 seconds
Default: 60

The following value specifies the time that the server waits for a client to respond to an oplock break request. Smaller values allow detection of crashed clients more quickly, but might potentially cause loss of cached data.

OplockBreakWait REG_DWORD 10 to 180 seconds
Default: 35

Note You must restart the computer for these registry changes to take effect.

How do I access the linksys WRE54g range expander’s web-based setup page? July 16, 2008

Posted by Cowboy in Uncategorized.
add a comment

http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=4103&lid=

If you’re using a Wireless-G Range Expander - WRE54G v2 or v3, you can do the following:

  1. Connecting the PC to LAN Port of the Range Expander
  2. Assigning a Static IP Address on your Wired Computer

NOTE: If you’re using WRE54G v1, click here.

A wired PC is a computer that you will directly connect to the router via Ethernet cable. The wired computer needs to have an Ethernet adapter to establish the connection to your range expander.

Connecting the PC to LAN Port of the Range Expander

Follow the steps below to connect the PC to the LAN port of the Linksys range expander.

Take an Ethernet cable and connect it to the computer. Take the other end of that same cable and connect it to LAN or Ethernet Port on top of the range expander.

Assigning a Static IP Address on your Wired Computer

Assign a static IP address on your wired computer. For instructions, click here.

To assign a static IP address on Mac, click here.

Accessing the Range Expander’s Web-Based Setup page

Access the range expander’s web-based setup page. For instructions, click here.

If you’re using a Wireless-G Range Expander - WRE54G v1, you need to do the following:

  1. Connecting Wirelessly to your Range Expander
  2. Assigning a Static IP Address on your Wireless Computer

How to clear Windows DNS cache without rebooting June 25, 2008

Posted by Cowboy in Uncategorized.
add a comment

ipconfig /flushdns

Using Remote Desktop on multiple machines on a LAN June 23, 2008

Posted by Cowboy in Uncategorized.
add a comment

Remote Desktop Ports

Windows Remote Desktop uses port 3389 to send and receive data. So the first computer being accessed remotely will be assigned this port to use for Remote Desktop. While the other computers in the local area network will be assigned sequential numbers starting with 3390. So, the second computer would be given port 3390, the third would use port 3391 and so on.

Follow the directions below to change the listening port for Remote Desktop and each computer you wish to access remotely.

1) Click on Start, Run
2) Type REGEDIT and press Enter
3) Click on the plus signs (+) next to the following sections in the Registry Editor

* HKEY_LOCAL_MACHINE
* System
* CurrentControlSet
* Control
* TerminalServer
* WinStations
* RDP-TCP

4) In the right-hand column find the section called PortNumber
5) Double-click on the name PortNumber
6) Choose the Decimal option under Base and type the correct port number using the information above.
7) Click OK
8) Close the Registry Editor
9) Repeat this procedure on each computer you wish to access remotely along with the steps involved in setting each computer up to use Remote Desktop.

Changing the Firewall to Allow Access

Now that each computer is assigned a unique port to use for Remote Desktop, you’ll have to tell the firewall running on each computer to allow that port through. Follow these steps to change the Windows Firewall to allow access.

1) In the Control Panel, click on the option for Security Center
2) Click on Windows Firewall under the heading “Manage Security Settings For”
3) Verify Windows Firewall is turned on
4) Click on the Exceptions tab
5) Click on the Add Port button
6) In the Name field, type REMOTE DESKTOP 2
7) In the Port field, type the port you assigned to the computer in the previous section: 3389, 3390, etc.
8) Choose TCP as the protocol and Click OK
9) Verify that there is a checkmark for the option REMOTE DESKTOP 2 and Click OK

Changing Your Router to Allow Access

Lastly, you’ll need to make a change in your router for each computer you want to access. This change is called Port Forwarding and a friend of mine has created a great site called PortForward.com to explain how to do this. Depending on your router the procedure is slightly different, however there are great tutorials on portforward.com to explain this.

Each computer you want to access must have its own static ip address on your network. There are two steps involved in setting a static IP address for each computer: discover your current ip address and assign the current ip address to your computer.

Discover the Current IP Address on your computer

1) Click on Start, Run
2) Type CMD and press Enter
3) At the blinking cursor, type IPCONFIG /ALL and press Enter (remember there is a space between IPCONFIG and /ALL)
4) Find the section for the Connected Ethernet Adapter and write down the following  information

* IP Address
* Subnet Mask
* Default Gateway
* DNS Servers

5) Type EXIT and press Enter to close the window

Assign the Current IP Address to Your Computer as a Static IP

1) Click on Start, Control Panel
2) In Classic View: Open Network Connections
In Category View: Select Network and Internet Connections, then click on Network Connections
3) Right-click on your active LAN or Internet connection
4) Click on Properties
5) In the General tab, highlight Internet Protocol (TCP/IP) and click Properties
6) Under the General tab, click Use the following IP Address and enter the information you wrote down in the previous section for this computer including

* IP address
* Subnet mask
* Default gateway

7) Click the option for Use the following DNS server addresses and enter the DNS servers your router is using
8) Click OK and then click OK again to leave the Network Settings section
9) Restart your computer
10) Follow the procedure above to check your current IP address and verify its the same as before
11) Finally, test the connection and make sure you can access the Internet.
Port Forward the Remote Desktop Port

Now you are ready to modify your router to port forward the remote desktop port number to the correct computer. Use the tutorials on PortForward.com to make changes to your router. Although the specific information will be different for your situation, you’ll forward the port you assigned for Remote Desktop to the static IP address you assigned for that particular computer. If you have three computers you are trying to reach with Remote Desktop, then you’ll have three entries in the port forward section of your router to accomplish this.

Also, its best if your internet connection to your LAN is assigned a static IP by your ISP. If you dont have a static IP, you will find it harder to connect because your IP will change each time your router is rebooted. To discover your current LAN IP, go to the website WhatIsMyIP.COM and it will show you your current IP.

As an alternative, you can sign up for a free Dynamic DNS account to track your IP and be able to access your network. You can sign up for DynDNS by visiting their site at http://www.dyndns.com

Using the Remote Desktop Connection to Connect to Each Computer

Now, you can test the remote desktop connections from another location.

1) On your laptop or another computer not connected to your LAN, open the Remote Desktop Connection software under Accessories and Communications
2) On the Remote Desktop screen type the IP of the network you want to connect to followed by a colon and the port number you wish to connect to.

Example: 215.76.43.5:3390

3) Finally click connect and see if you can reach your computer. If the connection is successful, you will be presented with the login screen for your computer, type your username and password and click Ok to access your computer.
4) Test this connection for each computer you wish to connect to behind your local area network.

NOTE: You’ll have to log into an account on your computer has been assigned a password. If you don’t have a password assigned, you’ll need to assign one before using Remote Desktop to connect.

Vista won’t let me unzip file May 30, 2008

Posted by Cowboy in Uncategorized.
add a comment

Right click on the downloaded file. select Properties, on the General tab, press
the Unblock button, Apply, and OK.

msoobe.exe Application Error May 30, 2008

Posted by Cowboy in Uncategorized.
add a comment

Insure your system date is valid.

Error: System not fully installed. Please run setup again. May 30, 2008

Posted by Cowboy in Uncategorized.
add a comment

originally from this site:

http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00024476&lc=en&cc=us&dlc=&product=71747&rule=915

HP and Compaq Desktop PCs - Error: System not fully installed. Please run setup again.

This document pertains to all HP and Compaq Desktop PCs with Windows XP.
After completing the initial setup process the PC will not start into Windows. The PC displays the following error:
System not fully installed. Please run setup again.
This error is typically caused when a recovery or the initial setup process is interrupted and not allowed to complete.
NOTE: Certain LCD flat panel monitors may prevent or delay the inital computer software setup. If you are using an LCD flat panel monitor, try attaching a conventional CRT monitor to perform the setup. Once the setup has been completed and you can use Windows, reconnect your LCD flat panel monitor.
NOTE: If this error occurs after perfroming a recovery, to prevent this message from re-appearing in the future, make sure that Windows Setup has finished. In some circumstance it may take several hours.
Resolution: Performing a Recovery
This error is best resolved by recovering all software using the recovery process. The recovery process may take a long time to complete, but it is the easiest method to resolve this issue. To start the recovery process, turn on the PC and press F10 repeatedly when the first screens appear. For more information about HP System Recovery, refer to HP and Compaq Desktop PCs - Performing an HP System Recovery in Windows XP .
CAUTION: Performing a Destructive Recovery will format the hard drive. This will delete all the information on the hard drive and reinstall Windows XP and the original software that came with the PC. Be prepared to reinstall software that was not originally included with the PC. You will also need to reconfigure an Internet Connection and obtain all critical Windows Updates, Virus definition updates, and anti-spyware updates.

Alternate method: Resetting System Setup
If you do not want to perform an HP system recovery, you can use the following steps to resolve this error:
Step 1: Opening a command prompt
Use the following steps to open a command prompt:
  1. Turn on the PC.
  2. Press the F10 key repeatedly at the first screen until a System Recovery screen appears.
    If a Welcome screen appears, click OK to continue.
  3. Click Advanced Options .
  4. Press the Alt + D keys to bring up the command prompt window
Step 2: Loading registry hive
Use the following steps to import a registry hive:
  1. At the command prompt enter the following: regedit
  2. Select HKEY_LOCAL_MACHINE .
  3. Click File , and then select Load Hive .
  4. Select the main drive letter (HP_Pavilion or Presario) from the “Look in:” dropdown field at the top of the Load Hive window.
  5. If a system32 error appears, click OK to continue.
  6. Browse to \windows\system32\config and double-click System .
    NOTE: If the system32 folder is empty, type the following into the File name field: \windows\system32\config\system
  7. In the “Key Name” field, type the following: temphive
  8. Click OK .
Step 3: Editing SystemSetupInProgress value
Use the following steps to edit the value:
  1. In the registry editor window, double-click HKEY_LOCAL_MACHINE , and then double-click temphive .
  2. Select the Setup key.
  3. Double-click the SystemSetupInProgress value in the right window.
  4. Change the “Value data:” field to a numerical zero “0″ and then click OK .
Step 4: Unloading the hive and saving
Use the following steps to unload the hive and exit:
  1. Select the temphive key in the left window.
  2. Click File , and then select Unload Hive .
  3. Close the Registry Editor and type the following at the command prompt: exit
  4. Press Enter , and then click Back in the Recovery screen.
  5. Click Quit to exit and restart.
    If this error occurred after installing software (not a recovery and not first time setup), you are finished.
Step 5: Resuming the PC setup process
Use the following steps to start the initial PC Setup process again:
  1. After Windows opens the desktop, click Start , Run , and enter the following into the Open field: c:\hp\bin\firstboot.txt
    The firstboot.txt file opens in Notepad.
  2. Click Edit , and then select Replace .
  3. Type a quotation mark ( ) into the “Find what:” field.
  4. Click Replace All .
  5. Delete the following text: [Commands]
  6. Click File and then Save As .
  7. Type firstboot.bat in the File name field.
  8. Make sure that path ends with the bin directory, and click the Save button.
  9. click Start , Run , and enter the following into the Open field: c:\hp\bin\firstboot.bat
  10. Click OK and do not touch the keyboard or mouse until the “Please Wait” screen closes.

Enable Remote Desktop Connection on Vista Home Premium May 22, 2008

Posted by Cowboy in Uncategorized.
1 comment so far

http://www.unet.fi/fransblog/2007/08/30/enable-remote-desktop-connection-on-vista-home-premium/

Enable Remote Desktop Connection on Vista Home Premium

Edit: I have now made a patch zip file for Vista SP1 available here: http://www.unet.fi/fransblog/wp-content/uploads/2008/03/termsrv_sp1.zip (hope it works for you, it did ok for my Home Premium SP1.)

There are many nice, but also quite many really irritating aspects to Windows Vista. Some are due to Microsoft intentionally crippling their own products. One of the most tiresome has been the disabling of Remote Desktop Connection. If you have to run down the stairs every time to check whether a particular process has ended or not, it gets old really quick, and double so when you realise that Vista Home Premium actually includes fully-featured Remote Desktop service, it is just broken by design. Here are the instructions to turn it back on — thanks a lot, guys!

Steps to Add Remote Desktop to Vista Home Premium:

1. Download termsrv.zip here
2. Extract Termsrv.zip to a temp directory
3. Start “Command Prompt” in Administrator mode (Run As Administrator)
4. Run the corresponding batch file for your Vista edition
5. Allow TCP Port 3389 on Windows Firewall or any other firewall product.
6. Done

Unofficial Windows 2000 Service Pack 5.1 May 18, 2008

Posted by Cowboy in Uncategorized.
add a comment

http://www.majorgeeks.com/download4817.html