LaserJet 1536dnf error 79

             

Phoned to tech support.

Switch off the device, then:
- press X and > simultaneously (keep pressed)
- switch on the printer
- keep pressed the two buttons and wait for the "restore" message on display
- wait... wait... when finished printer boot again
 

How To Mount USB flash drive from Command Line

Mounting a USB flash drive in GNOME (or another Linux desktop environment) is as easy as plug and play. Yet, occasionally, you need to mount one on a server which does not run X, then you must know how to do it on the command line.

1. Become root.
   
   

   $ sudo -s



2. Plug in USB drive to a USB port.


3. Identify the correct partition name corresponding to the USB drive.
   
   For my Debian system, it is sda, and partition 1.
   

   $ dmesg |grep -i 'SCSI device'
   ...
   SCSI device sda: 3903488 512-byte hdwr sectors (1999 MB)

   
   Alternatively,
   

    $ grep  SCSI /var/log/messages
   ...
   Dec  1 11:52:26 tiger kernel: SCSI device sda: 3903488 512-byte hdwr sectors (1999 MB)



4. Mount the partition to an existing mount point (directory).
   
   

   $ mkdir -p /mnt/myusb
   $ mount -t vfat -o rw,users /dev/sda1 /mnt/myusb

   
   users give non-root users the ability to unmount the drive.
   
   You can verify the drive is indeed mounted as follows:
   

    $ mount

   
   You should see a line in the output that looks like:
   

   /dev/sda1 on /mnt/myusb type vfat (rw,noexec,nosuid,nodev)

To retrieve the USB drive:

1. You must unmount the partition before physically unplugging the USB device.
   
   

   $ umount /mnt/myusb

   
   You can run the mount command again (with no argument) to verify that the volume is indeed mounted.


2. Unplug USB drive.

*******
readwrite you need

apt sources
deb http://archive.debian.org/debian/ lenny main non-free contrib

apt-get ntfs-3g

mount -t ntfs-3g /dev/sdb1 /mnt/myusb
umount /dev/sdb1

AudioCodes MP-114 - SAS (Stand Alone Survivability) configuration

[asterisk-users] AudioCodes MP-114 - SAS (Stand Alone Survivability) configuration

Joseph syscon780 at gmail.com
Wed Jan 13 18:23:09 CST 2010

---

SOLVED! 
Correct me anybody if I'm wrong but I think SAS option is for WAN only not for the case if AudioCodes MP and Asterisk are on the same network.

I was trying to configure the fail-over mode in scenarios:
- Asterisk sever goes down (doesn't happen very often, never happened to me but it could) 
- hardware failure 
- power loss etc.

(It seems to me Audiocodes caters MS and/or close source hardware; they have many "doc" files on their web-page but very little or none pertaining 
to Asterisk configuration with their hardware MediaPack), so here is my solution without going through 500-pages manual.
  
So in the above cases the calls should go through IN or OUT without interuptions, Audiocodes MP can be configured for fail-over mode; my old Liksys 3102 CAN 
NOT, when power goes down and Linksys is up, the calls will not go through. 

Here is the relevant configuration for the above scenario:


==================
Protocol Configuration -> Proxies/IpGroups/Registration -> Proxy & Registration -> 
Use Default Proxy: NO
Enable Fallback to Routing Table: Enable
Prefer Routing Table: NO
Enable Registration: Enable
Registrar IP Address: 10.0.0.109  (enter IP address of the asterisk server, very important)
Gateway Name: (none)
Gateway Registration Name: (none)
Subscription Mode: Per Endpoint
User Name: (none)
Password: Default_Passwd
Cnonce: Default_Cnonce
Authentication Mode: Per Endpoint

Routing Tables -> Routing General Parameters ->
Alt Routing Tel to IP Connectivity Method: SIP OPTION ; (in case asterisk and MP-114 are on the same network)

Tel to IP Routing ->  (your numbers and IP's will be different)
Src. Trunk Group ID  Dest. Phone Prefix  Source Phone Prefix  Dest. IP Address
*                    369                  *                    10.0.0.157
*                    *                    *                    10.0.0.109
*                    *                    *                    10.0.0.157

First line is for fax extension, there is no reason to forward it to asterisk, it should go directly to Hylafax (or your fax machine) regardless of 
asterisk status.
Without playing/entering all internal extensions, second line directs all calls to Asterisk sever. 
Third line is for fail-over mode in case of Asterisk failure, power failure, all calls are directed via to MP-114 so calls go IN and OUT without interruption 

In addition to these setting user must configure:

Routing Tables -> IP to Trunk Group Routing 
Endpoint Settings -> Authentication
Endpoint Settings -> Automatic Dialing
Endpoint Number -> EndPoint Phone Number
Hunt Group -> Hunt Group Settings

and Optionally: 
Manipulation Tables -> Dest Number IP->Tel
===================

-- 
Joseph

Change the IP address of an AudioCodes MP-112 VoIP Gateway

Change the IP address of an AudioCodes MP-112 VoIP Gateway

25 February, 2010 - 10:38 — tom8787

One of the useful elements in an all-IP environment is an AudioCodes VoIP gateway. The problem with the thing is the IP address. If you want to access it, but you don't have the IP address available, you can change it by using an analog telephone.
- Connect the phone to FXS port 1
- Pick up the phone, and dial ***12345
- Dial 1# to change the IP address
- A voice will spell the current address partially.
- Press #
- The system asks to enter the new IP address
- Enter the new address, use * for a . (so 127*0*0*1 for example)
- The system repeats the IP address entered
- Press 1 to save it
To change the subnet mask you have to choose #2, to change the default gateway you have to choose #3 in the beginning.
After this is done, you can log in using the web interface. Default username and password are Admin-Admin.

***
It is very simple reset device
then ip : 10.1.10.10
user : admin
pass ; admin
***
Use bootp software(Audio Codecs CD) send this config file

reset.ini
-----------------------
[SYSTEM Params]
RESETWEBPASSWORD
[BSP Params]
-----------------------

Run Control Panel Applets as Another User

How can I run Control Panel applets as another user (one with administrative privileges)?
Sometimes you'll want to do file and folder modifications, or even partition formatting, but you won't want to do it while logged on as an administrator.

Every Control Panel applet is in fact a file with a .CPL extension. If you perform a search for these files you'll see that they're all located in the %systemroot%\system32 folder.

1. Right-click any file and choose Run As.

1. A dialog box will pop-up asking you for a valid username and password. Enter one of a user that has the required administrative privileges to run and manage that applet.

1. If you gave a valid username and password the applet will open giving you the full permissions to manage it.

That's it!
BTW, it's time you got to know the RUNAS command that's now native in W2K and XP. Open a Command Prompt and run the following command:

runas /user:computername\Administrator command

where computername is the name of your computer, and username is the name of the user you're trying to run the command as (e.g. Administrator). The command is the command you're trying to run (e.g. a batch file, an .exe file or even a control panel applet).
For example, to open System from a command line as an administrator, type:

runas /user:computername\Administrator "rundll32.exe shell32.dll,Control_RunDLL sysdm.cpl"

For a list of some of the Control Panel applet filenames see this (incomplete) list:

Control Panel Applet	Filename
Accessibility	access.cpl
Add New Hardware	hdwwiz.cpl
Add/Remove Programs	appwiz.cpl
Date/Time Properties	timedate.cpl
Display Properties	desk.cpl
FindFast	findfast.cpl
Internet Properties	inetcpl.cpl
Joystick Properties	joy.cpl
Keyboard Properties	main.cpl
Local Users management	nusrmgr.cpl
Microsoft Exchange	mlcfg32.cpl
Microsoft Mail Post Office	wgpocpl.cpl
Modem Properties	modem.cplNote: In Windows NT 4.0, W2K, XP and Windows 2003 - Modem properties is telephon.cpl
Mouse Properties	main.cpl
Multimedia Properties	mmsys.cpl
Network Properties	netcpl.cplNote: In Windows NT 4.0, W2K, XP and Windows 2003 - Network properties is Ncpa.cpl
Password Properties	password.cpl
Power Options	powercfg.cpl
Regional Settings	intl.cpl
Sound Properties	mmsys.cpl
System Properties	sysdm.cpl

Each applet might have additional features. See the links on the right for more details.
Description of Control Panel (.cpl) Files - 149648

HP LaserJet 1020 Spooler Service Restart

UPDATE: The following procedure did not work for very long. See the new procedure.
If you are sharing an HP LaserJet 1020 USB printer over a network, and you have problems printing to it without restarting the print spooler service on the “server” machine (like people here, here and here are having), I found a solution that works for me. Maybe it will work for you too.

Quick Fix

Put the user who is printing to said printer over the network into the “Print Operators” group. If that doesn’t work (or you aren’t on an Active Directory domain – i.e. most users), try setting the security on the printer so that “Everyone” has “Print”, “Manage Printers”, and “Manage Documents” allowed. (Open up Printers/Faxes, Right click the printer, hit properties, hit the Security tab, select “Everyone”, put checkmarks in all the “Allow” boxes, hit OK.)
It may not be the most secure policy, but it sure beats buying another printer and then waiting around for the printer to get there. I find it makes a good “crutch” solution in a pinch.

Reason

The print driver on the 1020 is HOST based, not PCL based. The problem I was having was that anyone who was not an Administrator would trigger the issue. I surmise that the HOST based driver requires a certain level of permissions from the user in order to fire off the job properly. Weird, but now solved.

HP LJ 1020 Spooler Service Restart Revisited

My previous fix for the HP LaserJet 1020 Spooler Service Restart issue did not stick. Upon reboot of the server, the problem returned and was not correctable in the manner previously described.
I researched the issue again and found a Microsoft forum post where they actually fixed the issue. The fix goes as follows:

• NOTE: Do this on the machine connected to the printer.
• Run gpdedit.msc
• Go to “Local Computer Policies\Administrative Templates\Printers”
  • Set the setting “Allow print spooler to accept client connections” to “Enabled”
• Go to “User Configuration\Administrative Templates\Control Panel\Printers\”
  • Set the setting “Point and Print Restrictions” to “Disabled”
• Close the Group Policy Editor
• Go into the Printers and Faxes control panel, right click on the printer and hit properties.
• Click the “Ports” tab
• Uncheck “Enable Bidirectional Printing”
• Close the Printer panels/windows
• Run a command line, type in “gpupdate /force”, and hit enter

Fixed!
The forum fix was here.

*****
Unchecked ENABLE DIRECTIONAL SUPPORT - Printing from XP WORKS!

Advice to employees on the proper use of the System Administrator's valuable time

(In following examples, we will substitute the name "Ted" as the System Administrator)

• Make sure to save all your MP3 files on your network drive. No sense in wasting valuable space on your local drive! Plus, Ted loves browsing through 100+ GB of music files while he backs up the servers.
• Play with all the wires you can find. If you can't find enough, open something up to expose them. After you have finished, and nothing works anymore, put it all back together and call Ted. Deny that you touched anything and that it was working perfectly only five minutes ago. Ted just loves a good mystery. For added effect you can keep looking over his shoulder and ask what each wire is for.
• Never write down error messages. Just click OK, or restart your computer. Ted likes to guess what the error message was.
• When talking about your computer, use terms like "Thingy" and "Big Connector."
• If you get an EXE file in an email attachment, open it immediately. Ted likes to make sure the anti-virus software is working properly.
• When Ted says he coming right over, log out and go for coffee. It's no problem for him to remember your password.
• When you call Ted to have your computer moved, be sure to leave it buried under a year-old pile of postcards, baby pictures, stuffed animals, dried flowers, unpaid bills, bowling trophies and Popsicle sticks. Ted doesn't have a life, and he finds it deeply moving to catch a glimpse of yours.
• When Ted sends you an email marked as "Highly Important" or "Action Required", delete it at once. He's probably just testing some new-fangled email software.
• When Ted's eating lunch at his desk or in the lunchroom, walk right in, grab a few of his fries, then spill your guts and expect him to respond immediately. Ted lives to serve, and he's always ready to think about fixing computers, especially yours.
• When Ted's at the water cooler or outside taking a breath of fresh air, find him and ask him a computer question. The only reason he takes breaks at all is to ferret out all those employees who don't have email or a telephone.
• Send urgent email ALL IN UPPERCASE. The mail server picks it up and flags it as a rush delivery.
• When the photocopier doesn't work, call Ted. There's electronics in it, so it should be right up his alley.
• When you're getting a NO DIAL TONE message at your home computer, call Ted. He enjoys fixing telephone problems from remote locations. Especially on weekends.
• When something goes wrong with your home PC, dump it on Ted's chair the next morning with no name, no phone number, and no description of the problem. Ted just loves a good mystery.
• When you have Ted on the phone walking you through changing a setting on your PC, read the newspaper. Ted doesn't actually mean for you to DO anything. He just loves to hear himself talk.
• When your company offers training on an upcoming OS upgrade, don't bother to sign up. Ted will be there to hold your hand when the time comes.
• When the printer won't print, re-send the job 20 times in rapid succession. That should do the trick.
• When the printer still won't print after 20 tries, send the job to all the printers in the office. One of them is bound to work.
• Don't use online help. Online help is for wimps.
• Don't read the operator's manual. Manuals are for wussies.
• If you're taking night classes in computer science, feel free to demonstrate your fledgling expertise by updating the network drivers for you and all your co-workers. Ted will be grateful for the overtime when he has to stay until 2:30am fixing all of them.
• When Ted's fixing your computer at a quarter past one, eat your Whopper with cheese in his face. He functions better when he's slightly dizzy from hunger.
• When Ted asks you whether you've installed any new software on your computer, LIE. It's no one else's business what you've got on your computer.
• If the mouse cable keeps knocking down the framed picture of your dog, lift the monitor and stuff the cable under it. Those skinny Mouse cables were designed to have 55 lbs. of computer monitor crushing them.
• If the space bar on your keyboard doesn't work, blame Ted for not upgrading it sooner. Hell, it's not your fault there's a half pound of pizza crust crumbs, nail clippings, and big sticky drops of Mountain Dew under the keys.
• When you get the message saying "Are you sure?", click the "Yes" button as fast as you can. Hell, if you weren't sure, you wouldn't be doing it, would you?
• Feel perfectly free to say things like "I don't know nothing about that boneheaded computer crap." It never bothers Ted to hear his area of professional expertise referred to as boneheaded crap.
• Don't even think of breaking large print jobs down into smaller chunks. God forbid somebody else should sneak a one-page job in between your 500-page Word document.
• When you send that 500-page document to the printer, don't bother to check if the printer has enough paper. That's Ted's job.
• When Ted calls you 30 minutes later and tells you that the printer printed 24 pages of your 500-page document before it ran out of paper, and there are now nine other jobs in the queue behind yours, ask him why he didn't bother to add more paper.
• When you receive a 130 MB movie file, send it to everyone as a high-priority mail attachment. Ted's provided plenty of disk space and processor capacity on the new mail server for just those kinds of important things.
• When you bump into Ted in the grocery store on a Sunday afternoon, ask him computer questions. He works 24/7, and is always thinking about computers, even when he's at super-market buying toilet paper and doggie treats.
• If your son is a student in computer science, have him come in on the weekends and do his projects on your office computer. Ted will be there for you when your son's illegal copy of Visual Basic 6.0 makes the Access database keel over and die.
• When you bring Ted your own "no-name" brand PC to repair for free at the office, tell him how urgently he needs to fix it so you can get back to playing EverQuest. He'll get on it right away, because everyone knows he doesn't do anything all day except surf the Internet.
• Don't ever thank Ted. He loves fixing everything AND getting paid for it!