ERROR: undefined
OFFENDING COMMAND:

STACK:

The Windows computer is appending a ^D to the end of the job. The following steps should resolve this issue:

- Open the Printers control panel
- Right-click on the printer and select Properties
- Click the Postscript tab
- Click the Advanced button
- In the lower left corner, you will find the checkbox "Send CTRL+D after job"
- Uncheck the box, click OK, and click OK again to close the printer properties
- Test printing

On Windows XP:
- Open Printers and Faxes control panel
- Right-click on the printer and select Printing Preferences
- On the Layout tab, click Advanced...
- Double-click PostScript Options
- Set "Send CTRL-D After Each Job" to No
- Click OK, and click OK again to close the printing preferences
- Test printing

Here are the steps that should resolve the matter:

1. Delete the printer icon from your desktop
2. Go into your Hard Drive -> System Folder -> Preferences folder and delete "DAVE DT Print Preferences"
3. Reboot the computer
4. On startup, go under the Apple menu and select "DAVE".
5. Once this window opens, click on "Access" in the menu bar at the top, and choose "logon" (this is the most important part, you must login this way instead of via the chooser to fix the problem).
6. Here you will login to the domain using your domain username and password
7. Once you have logged on in this manner, go into the chooser and recreate the printer as before (you should not get prompted to login again when you select the server via the chooser).

We are looking into this issue for possible resolution in a future release of DAVE. It seems that the Windows postscript print driver does not format the postscript file correctly for the Macintosh to read. The Macintosh will recognize that the file is a postscript file, but because of the formatting, it will not recognize it as a print file.

Please try the following steps:

- On the Windows machine, go to Start-Settings-Printers
- Delete the printer
- Close the printer control panel and open the Network Neighborhood
- Double click on the name of the Macintosh sharing the printer
- Double click on the name of the printer
- Windows must set up the printer now. Click Yes.
- Click Next
- Configure the printer as a Apple LaserWriter and click Next
- Name the printer and click Next
- Click Finish and check for test page

This message could also read:

"\\<COMPUTERNAME> is not accessible.
The device does not exist on the network"

Try disabling any firewall software on the Macintosh to see if this makes a difference. If you are using Mac OS X, disable the built in firewall service. Many firewalls by default block the ports that DAVE uses for communication. The ports DAVE uses are ports 137,138,139, and 445 using both TCP and UDP.

Try changing the name of the Macintosh. A computer name can be up to 15 alphanumeric characters and cannot contain any illegal characters (eg. an apostrophe). It must be unique on the network.

If this does not work, stop DAVE Sharing, remove the shares, add them back in, and start the DAVE Sharing service again. Make sure that none of the share names are longer than 12 characters or have any illegal characters in the name.

This error occurs because Apple's Windows File Sharing option is not turned off, even when it appears that you have disabled it. The current workaround is to restart the Macintosh, open the Sharing preference and verify that Windows File Sharing is unchecked. Then, highlight Windows File Sharing and look at the button to the right and verify that it says "Start". If it doesn't say "Start", click the "Stop" button. You should then be able to install DAVE. This issue has been reported to Apple.

There are two causes of this error:

1. OS X 10.7, Lion, and the Firewall

In Lion, the built-in Firewall can cause ADmitMac or DAVE to report this error on installation.  This is a bug in the Firewall that has been reported to Apple.  To work around the issue, launch the System Preferences and click the Security & Privacy pane.  On the Firewall tab, stop the Firewall, then reboot the Mac.  You should then be able to install ADmitMac or DAVE.

2. Windows File Sharing

If SMB (Windows) File Sharing is active, you will need to turn it off before installing ADmitMac or DAVE.  To do so, launch the System Preferences and click the Sharing pane.  With File Sharing selected, click the Options button, then uncheck the "Share files and folders using SMB (Windows)" checkbox.  After restarting the Mac, you will be able to install ADmitMac or DAVE.

This is usually caused by a memory allocation problem on the windows computer, where the machine does not have enough resources or memory available to respond to a connection request by the Macintosh. If more than one machine is connecting to the windows computer, it may not have enough resources available to allow one more machine to connect. You can resolve this issue by increasing the IRPStackSize value in the registry. You can find instructions on how to do this in Microsoft Knowledge Base Article - 177078. Below is the link to Microsoft's article on this issue:

http://support.microsoft.com/default.aspx?scid=kb;en-us;177078

Another possible solution would be to increase the amount of ram on the Windows computer. Finally, In rare cases we have found that some older antivirus software may also cause this to occur. A quick way to test this would be it disable the antivirus software and see if the problem goes away. If this does resolve the problem, you may want to see if there is an update to your antivirus software.

To update ADmitMac to the latest version, you must run the installer while logged in to a local admin account. If you run the installer while logged in to a domain account, the installation might fail or cause damage to your domain account.

If you have already run the installer while logged in to a domain account, please log in with a local admin account and run the installer again. If the Setup Assistant runs automatically after the installer quits, please click through it - confirming settings - until it completes.

There are three possible causes for this.

1. If you are using a network home folder, make sure that your domain account has not met the disk quota available to you. There is a known issue where if your home folder grows in size and nears, or has reached, the amount of hard disk space alloted to your domain account, you will not receive a disk quota warning. Instead, once the disk quota is met, you will no longer be able to save files to your home folder.

2. If your home folder was recently moved to a different location, make sure that your domain account is the owner of your home directory.

3. If you are using a local home folder, and login to different domains, make sure that the username for your domain account is not identical on more than one domain. The name of your home folder will be the same as the username you use to login to the domain. The first time you login to your domain, your domain account for that domain will be the owner of the home folder. If you login to another domain using the same username, ADmitMac will try to use the home folder from the previous login.

Because the accounts are different, the new domain account will not be the owner of the home folder and will not have the necessary permissions for it. However, this new domain account will not be the owner of this home folder.

This error may occur when trying to save changes in Workgroup Manager on a Macintosh that also has ADmitMac installed. One possible cause for this problem may be that the Mac OS X machine experiencing this problem may have the LanMan Policy security set too low. Verify that LanMan policy in the ADmitMac Directory Access plugin is set to an option that includes authenticating via NTLMv2.

In Mac OS X v10.5 (Leopard), Apple made some significant changes to the Mac OS Finder and the Sidebar, and these changes persist in Mac OS X v10.6 (Snow Leopard). You will not be able to access Windows servers through the sidebar, but will be able to access the volumes once you have mounted them using either the ADmitMac Browser, or by entering the path into the Server Address field in "Go - Connect to Server". We have been made to understand that it is a bug in the Finder that keeps network volumes from working properly in the Sidebar, and that Apple is working to resolve it.

In the Finder Preferences (General), make sure that "Connected Servers" is checked. Also in the Finder Preferences (Sidebar), make sure that "Computer" is selected.

Once a volume is mounted, you can access by opening from the Desktop, or by selecting "Computer" in the sidebar, then the mounted volume.

To update ADmitMac to the latest version, you must run the installer while logged in to a local admin account. If you run the installer while logged in to a domain account, the installation might fail or cause damage to your domain account.

If you have already run the installer while logged in to a domain account, please log in with a local admin account and run the installer again. If the Setup Assistant runs automatically after the installer quits, please click through it - confirming settings - until it completes.