Windows 7 64Bit Installation

[holodyn]

For those of you that have experienced problems installing XAMPP 1.7.4 onto Windows 7 64-bit, here is the result of a hour of head banging.

** INSTALL **
1) Download the XAMPP ZIP or 7z Package (Not the Installer)
2) Extract the Package onto your C: (the zip file contains a xampp folder, move that into the C: root)
3) EDIT YOUR HOSTS FILE to check if "localhost" is correctly mapped to the local IP 127.0.0.1
- the hosts file is located at c:/Windows/System32/drivers/etc/hosts
- you will need to edit as administrator (right click Notepad, Run as Administrator, Open File)
- Add (if not already present) the line: "127.0.0.1 localhost"

** Optional Install of APACHE / MySQL as a SERVICE **
a) Run c:/xampp/apache/apache_installservice.bat (right click, Run as Administrator)
b) Run c:/xampp/mysql/mysql_installservice.bat (right click, Run as Administrator)

** Load Control Panel **
a) Run c:/xampp/xampp-control.exe (After the above, the errors I was experiencing with the control panel were gone)

** Test your Installation **
a) Load http://localhost/xampp/ in your browser
b) Click Status

I hope this helps - I was about to abandon XAMPP after several years of using this great package. It just needed a little TLC.

Cheers

[holidaysinrome]

Your method does not work (
Hello

[holidaysinrome]

This is the file I have on C, where I have to change, step by step what I did there on the topic but could not :

3) EDIT YOUR HOSTS file to check if "localhost" is Correctly mapped to the local IP address 127.0.0.1
- the hosts file is located at c: / ​​Windows/System32/drivers/etc/hosts
- you will need to edit as administrator (right click Notepad, Run as Administrator, Open File)
- Add (if not Already present) the line: "127.0.0.1 localhost"

File on the computer where I have to change? thanks:

----------------------------------------------------------------------------------------
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP / IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry Should Be Kept on an individual line. Should the IP address
# Placed in the first column be Followed by the Corresponding host name.
# The IP address and the host name separated by at least Should Be One
# space.
#
# Additionally, comments (Such as These) May be inserted on individual
# Following lines or the machine name denoted by a '#' symbol.
#
# For example:
#
# # source server 102.54.94.97 rhino.acme.com
# # x client host 38.25.63.10 x.acme.com

# localhost Within DNS name resolution is handled itself.
# 127.0.0.1 localhost
#:: 1 localhost

127.0.0.1 activate.adobe.com
------------------------------------------------------------------------------------------------------

[WilliL]

you've the right file - just append the line: 127.0.0.1 localhost

----------------------------------------------------------------------------------------
# Copyright (c) 1993-2009 Microsoft Corp.
#
# lines deleted WilliL
#
# localhost Within DNS name resolution is handled itself.
# 127.0.0.1 localhost
#:: 1 localhost

127.0.0.1 activate.adobe.com
#------------------------------------------------------------------------------------------------------
127.0.0.1 localhost # this line appended local host for XAMPP

[holidaysinrome]

Thanks for the reply, I replaced the file "hosts" that you wrote this with you:
-------------------------------------------------- ------
-------------------------------------------------- --------------------------------------
# Copyright (c) 1993-2009 Microsoft Corp.
#
# lines deleted WilliL
#
Within localhost # DNS name resolution is handled itself.
# 127.0.0.1 localhost
#:: 1 localhost

127.0.0.1 activate.adobe.com
#------------------------------------------------- -------------------------------------------------- ---
127.0.0.1 localhost # this line appended local host for XAMPP


but it always gives me error, if I control ** ** Test your Installation
a) Load http://localhost/xampp/ in your browser
b) Click Status
tells me that everything works;-)
joomla when I transfer files in the folder "htdocs" part of the installation and all is well,
but then when I type http://localhost to see the site locally from my mistake.
Where is that wrong?
Xampp is the folder in "C"

The control panel of XAMPP I get this error:
XAMPP Component Status Check Failure (-2)
Current directory: c: xampp
Run this program only from your XAMPP root director

[holidaysinrome]

The errors are these:

ict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 29

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 32

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 138

Strict Standards: Non-static method JRequest::clean() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 33

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\libraries\joomla\environment\request.php on line 463

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\libraries\joomla\environment\request.php on line 464

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\libraries\joomla\environment\request.php on line 465

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\libraries\joomla\environment\request.php on line 466

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\libraries\joomla\environment\request.php on line 467

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in C:\xampp\htdocs\libraries\joomla\environment\request.php on line 468

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 35

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 38

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 39

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 46

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 47

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 50

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 53

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 54

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 57

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\joomla\import.php on line 58

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 138

Strict Standards: Non-static method JFactory::getApplication() should not be called statically in C:\xampp\htdocs\index.php on line 31

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 138

Strict Standards: Redefining already defined constructor for class JObject in C:\xampp\htdocs\libraries\joomla\base\object.php on line 57

Strict Standards: Non-static method JApplication::getInstance() should not be called statically in C:\xampp\htdocs\libraries\joomla\factory.php on line 46

Strict Standards: Non-static method JLoader::import() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in C:\xampp\htdocs\libraries\loader.php on line 161

Etc......................................................................................

[Altrea]

Which version of joomla?
Are your sure your version of Joomla can work with PHP 5.3?

[holidaysinrome]

Joomla 1.5.23
Operating system on pc windows seven
Thank you

[Altrea]

Okay, good news:

The Joomla 1.5.23 CAN work with PHP 5.3 (sure, some Joomla extensions are not able to work with PHP 5.3)

To bring it to work you have to configure your php error_reporting.
Please open your \xampp\php\php.ini file in the editor of your choice and search for "error_reporting".
There must be a block of comments about the error_reporting and some lines below is the setting.

Please post the value of this error_reporting setting to see if the strict standards are set in your php.ini or inside your joomla files.

[holidaysinrome]

Hello, here is under the complete file.
One question, if I use joomla 1.6 from the same problems?
Thanks


[PHP]

;;;;;;;;;;;;;;;;;;;
; About php.ini ;
;;;;;;;;;;;;;;;;;;;
; PHP's initialization file, generally called php.ini, is responsible for
; configuring many of the aspects of PHP's behavior.

; PHP attempts to find and load this configuration from a number of locations.
; The following is a summary of its search order:
; 1. SAPI module specific location.
; 2. The PHPRC environment variable. (As of PHP 5.2.0)
; 3. A number of predefined registry keys on Windows (As of PHP 5.2.0)
; 4. Current working directory (except CLI)
; 5. The web server's directory (for SAPI modules), or directory of PHP
; (otherwise in Windows)
; 6. The directory from the --with-config-file-path compile time option, or the
; Windows directory (C:\windows or C:\winnt)
; See the PHP docs for more specific information.
; http://php.net/configuration.file

; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.

; Directives following the section heading [PATH=/www/mysite] only
; apply to PHP files in the /www/mysite directory. Directives
; following the section heading [HOST=www.example.com] only apply to
; PHP files served from www.example.com. Directives set in these
; special sections cannot be overridden by user-defined INI files or
; at runtime. Currently, [PATH=] and [HOST=] sections only work under
; CGI/FastCGI.
; http://php.net/ini.sections

; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
; Directives are variables used to configure PHP or PHP extensions.
; There is no name validation. If PHP can't find an expected
; directive because it is not set or is mistyped, a default value will be used.

; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), a quoted string ("bar"), or a reference to a
; previously set variable or directive (e.g. ${foo})

; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; ^ bitwise XOR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT

; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.

; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:

; foo = ; sets foo to an empty string
; foo = None ; sets foo to an empty string
; foo = "None" ; sets foo to the string 'None'

; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.

;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; PHP comes packaged with two INI files. One that is recommended to be used
; in production environments and one that is recommended to be used in
; development environments.

; php.ini-production contains settings which hold security, performance and
; best practices at its core. But please be aware, these settings may break
; compatibility with older or less security conscience applications. We
; recommending using the production ini in production and testing environments.

; php.ini-development is very similar to its production variant, except it's
; much more verbose when it comes to errors. We recommending using the
; development version only in development environments as errors shown to
; application users can inadvertently leak otherwise secure information.

;;;;;;;;;;;;;;;;;;;
; Quick Reference ;
;;;;;;;;;;;;;;;;;;;
; The following are all the settings which are different in either the production
; or development versions of the INIs with respect to PHP's default behavior.
; Please see the actual settings later in the document for more details as to why
; we recommend these changes in PHP's behavior.

; allow_call_time_pass_reference
; Default Value: On
; Development Value: Off
; Production Value: Off

; display_errors
; Default Value: On
; Development Value: On
; Production Value: Off

; display_startup_errors
; Default Value: Off
; Development Value: On
; Production Value: Off

; error_reporting
; Default Value: E_ALL & ~E_NOTICE
; Development Value: E_ALL | E_STRICT
; Production Value: E_ALL & ~E_DEPRECATED

; html_errors
; Default Value: On
; Development Value: On
; Production value: Off

; log_errors
; Default Value: Off
; Development Value: On
; Production Value: On

; magic_quotes_gpc
; Default Value: On
; Development Value: Off
; Production Value: Off

; max_input_time
; Default Value: -1 (Unlimited)
; Development Value: 60 (60 seconds)
; Production Value: 60 (60 seconds)

; output_buffering
; Default Value: Off
; Development Value: 4096
; Production Value: 4096

; register_argc_argv
; Default Value: On
; Development Value: Off
; Production Value: Off

; register_long_arrays
; Default Value: On
; Development Value: Off
; Production Value: Off

; request_order
; Default Value: None
; Development Value: "GP"
; Production Value: "GP"

; session.bug_compat_42
; Default Value: On
; Development Value: On
; Production Value: Off

; session.bug_compat_warn
; Default Value: On
; Development Value: On
; Production Value: Off

; session.gc_divisor
; Default Value: 100
; Development Value: 1000
; Production Value: 1000

; session.hash_bits_per_character
; Default Value: 4
; Development Value: 5
; Production Value: 5

; short_open_tag
; Default Value: On
; Development Value: Off
; Production Value: Off

; track_errors
; Default Value: Off
; Development Value: On
; Production Value: Off

; url_rewriter.tags
; Default Value: "a=href,area=href,frame=src,form=,fieldset="
; Development Value: "a=href,area=href,frame=src,input=src,form=fakeentry"
; Production Value: "a=href,area=href,frame=src,input=src,form=fakeentry"

; variables_order
; Default Value: "EGPCS"
; Development Value: "GPCS"
; Production Value: "GPCS"

;;;;;;;;;;;;;;;;;;;;
; php.ini Options ;
;;;;;;;;;;;;;;;;;;;;

[Altrea]

these are just the comments.
important is the setting (in mine php.ini file thats line 516. should be somewhere around that line in yours too)

Code: Select all

error_reporting = E_ALL | E_STRICT

I don't know if Joomla 1.6 has the same issues. Just try it. costs only 5 minutes to find that out.
Joomla installation is quite fast and easy.

[holidaysinrome]

Thank you, this is the part that you ask?

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; This directive informs PHP of which errors, warnings and notices you would like
; it to take action for. The recommended way of setting values for this
; directive is through the use of the error level constants and bitwise
; operators. The error level constants are below here for convenience as well as
; some common settings and their meanings.
; By default, PHP is set to take action on all errors, notices and warnings EXCEPT
; those related to E_NOTICE and E_STRICT, which together cover best practices and
; recommended coding standards in PHP. For performance reasons, this is the
; recommend error reporting setting. Your production server shouldn't be wasting
; resources complaining about best practices and coding standards. That's what
; development servers and development settings are for.
; Note: The php.ini-development file has this setting as E_ALL | E_STRICT. This
; means it pretty much reports everything which is exactly what you want during
; development and early testing.
;
; Error Level Constants:
; E_ALL - All errors and warnings (includes E_STRICT as of PHP 6.0.0)
; E_ERROR - fatal run-time errors
; E_RECOVERABLE_ERROR - almost fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_STRICT - run-time notices, enable to have PHP suggest changes
; to your code which will ensure the best interoperability
; and forward compatibility of your code
; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
; E_DEPRECATED - warn about code that will not work in future versions
; of PHP
; E_USER_DEPRECATED - user-generated deprecation warnings
;
; Common Values:
; E_ALL & ~E_NOTICE (Show all errors, except for notices and coding standards warnings.)
; E_ALL & ~E_NOTICE | E_STRICT (Show all errors, except for notices)
; E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR (Show only errors)
; E_ALL | E_STRICT (Show all errors, warnings and notices including coding standards.)
; Default Value: E_ALL & ~E_NOTICE
; Development Value: E_ALL | E_STRICT
; Production Value: E_ALL & ~E_DEPRECATED
; http://php.net/error-reporting
error_reporting = E_ALL | E_STRICT

; This directive controls whether or not and where PHP will output errors,
; notices and warnings too. Error output is very useful during development, but
; it could be very dangerous in production environments. Depending on the code
; which is triggering the error, sensitive information could potentially leak
; out of your application such as database usernames and passwords or worse.
; It's recommended that errors be logged on production servers rather than
; having the errors sent to STDOUT.
; Possible Values:
; Off = Do not display any errors
; stderr = Display errors to STDERR (affects only CGI/CLI binaries!)
; On or stdout = Display errors to STDOUT
; Default Value: On
; Development Value: On
; Production Value: Off
; http://php.net/display-errors
display_errors = On

[Altrea]

Exactly!

go to the lines:

Code: Select all

; Production Value: E_ALL & ~E_DEPRECATED
; http://php.net/error-reporting
error_reporting = E_ALL | E_STRICT


and change them to:

Code: Select all

; Production Value: E_ALL & ~E_DEPRECATED
; http://php.net/error-reporting
error_reporting = E_ALL & ~E_NOTICE


(only the last line is changed here. the other ones are just for your orientation.)

After the change, restart your Apache.

[holidaysinrome]

Perfect !!!!!!!!!!!!!! Works great !!!!!!!!!!
Thanks