Question: Does Pure ASP Upload support uploading large files on Windows 2003 server? I'm getting the following error:

---

Request object error 'ASP 0104 : 80004005'
Operation not Allowed
/ScriptLibrary/incPureUpload.asp, line 40

Answer:

---

Yes, Pure ASP Upload supports uploading large files on the Windows 2003 server. However:
IIS6.0 prevent the upload of files more than +200Kb. So you need to make some changes in the default IIS settings first.

Background

---

For IIS6.0 users, the AspMaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of an ASP request. If a Content-Length header is present and specifies an amount of data greater than the value of AspMaxRequestEntityAllowed, IIS returns a 403 error response.

This property is related in function to MaxRequestEntityAllowed, but is specific to ASP request. Whereas you might set the MaxRequestEntityAllowed property to 1 MB at the general World Wide Web Publishing Service (WWW Service) level, you may choose to set AspMaxRequestEntityAllowed to a lower value, if you know that your specific ASP applications handle a smaller amount of data.

Solution

---

Open your metabase.XML which is located in c:\Windows\System32\Inetsrv find the line "AspMaxRequestEntityAllowed" and change it to "1073741824". This is 1GB - of course you can enter another value to suite your needs.



org. location

You can enable logging with Group Policies by editing the appropriate OU or Directory Group Policy. Under Group Policy, expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then select Windows Installer.

Double-click Logging, and then click Enabled. In the Logging box, enter the options you want to log. The log file, Msi.log, appears in the Temp folder of the system volume.

For more information about MSI logging, please see Windows Help. To do so, search using the phrase "msi logging" and select "Managing options for computers through Group Policy".

Open the registry with Regedit.exe and create the following path and keys:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmup
The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 1.1:
v - Verbose output
o - Out-of-disk-space messages
i - Status messages
c - Initial UI parameters
e - All error messages
w - Non-fatal warnings
a - Start up of actions
r - Action-specific records
m - Out-of-memory or fatal exit information
u - User requests
p - Terminal properties
+ - Append to existing file
! - Flush each line to the log

"*" - Wildcard, log all information except for the v option. To include the v option, specify "/l*v".
Note This should be used only for troubleshooting purposes and should not be left on because it will have adverse effects on system performance and disk space. Each time you use the Add/Remove Programs tool in Control Panel, a new Msi*.log file is created.

CISCO SEARCH ...



CISCO FORUMS / SEARCH / Search Results for "vpn dmz " within "All Forums"



FORUM: General: VPN access to DMZ host



FORUM: Security: Remote access VPN client for PIX



MCSE: Questions involving DMZ-VPN on 515



MCSE: VPN access to DMZ through other Network



MCSE: Limiting access inside a VPN TUNNEL

Generate the PIX Firewall RSA key pair
ca generate rsa key 2048
Save keys and certificates, and the CA commands (except those indicated) in Flash memory
ca save all
write memory

Hi, and thanks for reading this HOWTO! Although these instructions are made for Fedora Core 2, they will more than likely work on any machine that has RPM support such as Mandrake, Suse, etc.

Requirements:
--------------------
1. You need to have at least a small knowledge on working the terminal and some basic commands that you will use.

First off, you will need to download the RPM from Sun's web site (http://www.java.com)
The file will be called something similar to j2re1_4_2_05-linux-i586-rpm.bin. After downloading the package for the VM, put it in a place where you can find it from the terminal such as your home directory.

Next, open a terminal session and do an SU to become root and enter the root password.
$ su
$ password: ******
# cd /home/kevin

Navigate to the directory using cd where you saved the RPM (EX: cd /home/kevin/)

Use the following command to run the self-installer.
# ./j2re1_4_2_05-linux-i586-rpm.bin (or whatever the package name is)

Then, read the agreement, pressing space to scroll down until you are at the end of the document. Type "yes" to agree to the license agreement. This will create an actual RPM in the same directory that you downloaded the RPM Binary.

After agreeing to the license, you will verify you know the name of the file using the dir command. The RPM should be called j2re1_4_2_05-linux-i586.rpm or similar according to the version you have downloaded.

Now, you are going to want to install the RPM for the VM, still as root, type the following command:

# rpm -ivh j2re1_4_2_05-linux-i586.rpm (or whatever the name of the file is)

If this is done correctly you should see something saying that it was completed with 100%.

CRUCIAL PART OF THE PROCESS:
---------------------------------------------------

I have had a lot of problems with making the Java VM work under FC2, because when you install the RPM, it actually doesn't make it work, it just installs it. So here is the steps to make the VM the default java vm for the OS:

First, make sure to have a terminal open and logged in using the SU command by entering the root password.

Then verify the directory that you have java installed under by doing this:

$ cd /usr/java
$ ls

You should see that there is a directory called j2re1.4.2 or something similar. If not, try this installing the RPM again, maybe something didn't go right.

Then you will have to remove all the default java associations by doing the following:

# cd /usr/bin
# rm java javac jar

If you get an error in removing any of the files java, javac, OR jar, it's okay, it's just to make sure you remove them. You will have to confirm to remove these files by typing a y at the prompt.

Next, you will have to create a link between the newly installed VM and the defaults for FC2 java vm by using the following command:

# cd /usr/bin
# ln -s /usr/java/j2re1.4.1_01/bin/java java

Be sure to replace the /usr/java/j2re1.4.1_01/bin java with whatever version you are running, but it should always point to the /bin/java directory under that folder.

Now, you should have a clear link between the two files so that you can install programs that require a Java VM installed.

If you are wanting to install LimeWire, enable java in Firefox or Mozilla, then read further, otherwise, Congratulations, you now have Sun's Java VM installed and configured.

LimeWire Install Instructions:
---------------------------------------

Since you have already installed the Java VM, all you should need to do now is navigate to the directory where you downloaded the Binary and type the following command:

$ sh ./LimeWireLinux.bin

After that, the program should install normally.


Firefox Instructions:
--------------------------

Navigate to the directory where Firefox is installed using the cd command as root in a terminal. Then you will see another directory called plugins, go to this directory and type this command while in the ./plugins directory of your firefox installation:

# ln -s /usr/java/j2re1.4.1_01/plugin/i386/ns610-gcc32/libjavaplugin_oji.so

This will create a link from the java vm to Firefox plugins, to test the browser, simply go to a web site that requires java installed, such as http://www.java.com

Mozilla Instructions:
--------------------------

To install the java vm for mozilla, simply use the Firefox instructions, with the exception of the directory where mozilla is installed. Then go to the ./plugins directory as above and create a link using the command above.

In den PHM Registry Editor auf dem Smartphone (muss zuvor installiert werden) wechseln.
Nun begebt euch in:
"HKCU/Software/T-Mobile/t-zones"
dort könnt ihr den Key URL verändern und so die Taste auf jede beliebige URL verlinken.

Sie können einen Hartwarereset probieren (WICHTIG - dabei gehen alle Daten verloren - also vorher eine Datensicherung durchführen):

Gerät aus
Beide Aktionstasten gleichzeitig gedrückt halten (die mit dem Strich unter dem Display links und rechts Außen)
Power einmal kurz drücken und beide Aktionstasten weiter gedrückt halten
bis ein schwarzer Bildschirm erscheint
dann "Press 0 to restore.... " mit 0 Bestätigen

Converting Windows Media Audio files into MP3 format is rather easy with mplayer and lame. My car stereo plays MP3s, so WMA is of no use to me!

This code is based on this script but I have to wonder why they overwrote the wma file?
Piping the output of mplayer into lame is left as an easy lesson for the reader!

for i in *.wma ; do mplayer -vo null -vc dummy -af resample=44100 -ao pcm -waveheader "$i" && lame -m j -h --vbr-new -b 160 audiodump.wav -o "`basename "$i" .wma`.mp3"; done; rm -f audiodump.wav

---

In case you don’t want the big temporary file, you can use a fifo. Here’s my script:
#!/bin/bash
#
# Dump wma to mp3

for i in *.wma
do
if [ -f $i ]; then
rm -f “$i.wav”
mkfifo “$i.wav”
mplayer -vo null -vc dummy -af resample=44100 -ao pcm -waveheader “$i” -aofile “$i.wav” &
dest=`echo “$i”|sed -e ’s/wma$/mp3/’`
lame -h -b 192 “$i.wav” “$dest”
rm -f “$i.wav”
fi
done

Comment by Scott Carlson — Monday, August 22nd, 2005 @ 1:04 am 

---

The latest version of mplayer complains about -ao pcm -waveheader - actually, it just needs to be replaced with -ao pcm:waveheader, and everything works again. Btw, thanks for the instruction, it is both useful and educational ;)

Comment by Petar — Wednesday, September 14th, 2005 @ 11:06 am

---

#

For latest versions of mplayer (on Fedora Core 4), you will need the following instead:

for i in *.wma
do
filename=`basename "$i" .wma`

#Rip with Mplayer / encode with LAME
echo "Ripping $i"
mplayer -quiet -vo null -vc dummy -af volume=0,resample=44100:0:1 -ao pcm:waveheader "$i"
echo "Encoding $i to "$filename".mp3"
lame -quiet -m s audiodump.wav -o "$filename".mp3

rm audiodump.wav
done

Comment by Ranchan — Thursday, December 1st, 2005 @ 12:15 am

---

#

On SuSE 9.3, (MPlayer 1.0-pre7) got it working (with the FIFO) sweetly with


#!/bin/bash
#
# Dump wma to mp3
for i in *.wma
do
if [ -f "$i" ]; then
rm -f "$i.wav"
mkfifo "$i.wav"
mplayer -quiet -vo null -vc dummy -af volume=0,resample=44100:0:1 -ao pcm:waveheader:file="$i.wav" "$i" &
dest=`echo "$i"|sed -e 's/wma$/mp3/'`
lame -V0 -h -b 160 --vbr-new "$i.wav" "$dest"
rm -f "$i.wav"
fi
done

I like hq VBR, but you can change the lame settings as you like. Note the MPlayer settings have changed.

Comment by Peter Ndiku — Friday, December 2nd, 2005 @ 12:52 pm

---

Org. Link