204 Benutzer online
06. November 2024, 04:28:49

Windows Community



 Antworten / AufrufeThemen mit dem Stichwort very
2
Antworten
6568
Aufrufe
Failed to query TCP/IP settings
Begonnen von charlotba
04. September 2010, 20:56:46
Hello Everyone,

I recently reinstalled Windows XP SP 2 as my PC was very sluggish and I don't recall ever doing a reinstall since I bought this PC six years ago!

I ran the File and Settings Transfer Wizard prior to my reinstall.

The install went smoothly and I transferred my original setting back to my PC after the install.

However, since the reinstall I'm unable to connect to the Internet and I'm also having problems connecting my wireless printer.

I connect to the Internet through a cable modem.

I also have a NETGEAR wireless router which connects my laptop and my Canon Pixma MX860.

I can still connect to the Internet with my laptop and can access the web as well as the Optonline.net mail server
.
I ran the new connection Wizard selecting "connect to the Internet" then "set up my connection manually" then "connect using a broadband connection that is always on".

The next screen read "completing the new connection Wizard, your broadband connection should already be configured and ready to use…".

However, when I use Internet explorer to try to access the web I get an error message that reads "the page cannot be displayed, the page you are looking for is currently unavailable…".

This same error message also recommends checking the option to "automatically detect settings" which I already had checked.

I've also done the following but still cannot connect:

- I right clicked the 1394 network connection and clicked "repair" and got the following error "failed to query TCP/IP settings of the connection".

- I looked at my bios settings to ensure that the integrated NIC card was set to "ON".

- Per a user that was having a similar problem, I renamed my TCPIP.sys files to TCPIP.sys.old and rebooted and retried the new connection but still had the same problem.I did notice that new TCPIP.sys files were created.

- I deleted the 1394 net adapter in the settings under system/device manager and reinstalled it by right clicking "network adapters" and selected "scan for hardware changes".

- I noticed there are all yellow question marks next to "other devices" and all the devices listed under that including ethernet controller, multimedia audio controller, multimedia controller, PCI modem, and video controller.

- Unplugged and then plugged in my cable modem to reset it.

I noticed when I right-clicked Network Connections/1394 communication 3 properties/Internet protocol (TCP/IP) there is a button to "install" as well as "properties" but the "uninstall" button is grayed out, does that mean that TCP/IP is not installed on this PC?

When I click "properties" the option to "obtain an IP address automatically" was checked off.

Does this mean that TCP/IP is in fact installed on this PC? The Uninstall button being grayed out leads me to believe TCP/IP is not installed on the PC.

Does all this have anything to do with why I can't get my wireless printer to connect wirelessly? The only other thing I can try is to reinstall the operating system but I'm trying to avoid that as it takes so long. Regarding the reinstall, I was doing it from an Dell OEM disk which had an option to install other Windows components and IIS was one of those components.

I don't recall the exact description however it had something to do with Internet connections and TCP/IP. However, when I tried to install it I was prompted for a second Windows install disk but my PC only came with the one install disk.

Is that IIS software something I can download from Microsoft and will that fix my problem?

Thanks in advance for any info you can provide!

Dan G. in CT

windowswindows vistavista problemproblem bgebge go-windowsgo-windows problemeprobleme ymsyms ohneohne dateidatei gehtgeht fehlerfehler winwin internetinternet 20082008 bgqbgq datendaten forfor win7win7 5818717858187178 yahooyahoo zwuzwu 4152442941524429 4870560848705608 funktioniertfunktioniert 5715546957155469 forumforum hilfehilfe computercomputer 5796724757967247 systemsystem
3
Antworten
8056
Aufrufe
PDF in Word-Datei umwandeln...
Begonnen von bavarianteacher
13. August 2010, 14:51:57
Wie geht das?
Es handelt sich um sehr große Dateien, ca. 500 Seiten.
Welche Software bewältigt das zuverlässig, dh. ohne Buchstabensalat, so dass auch die Textform genauso in Word übertragen wird, wie im Original der PDF.
Habe schon "Free PDF in Word Converter" probiert, das haut nicht hin! ?(

Bitte um Hilfe!
Danke!
13
Antworten
19560
Aufrufe
Windows Search indizierung extrem langsam
Begonnen von buzzbomb
05. Februar 2010, 19:10:02
Hallo,
ich habe ein Problem mit der indizierung der Dateien für Win Search. Da ich die für Outlook brauche kann ich leider nicht darauf verzichten. Bisher gab es damit auch nie Probleme, nun nachdem ich alle Dateien neu indizieren lassen wollte, läuft die indizierung nur sehr langsam, in 24 Stunden konnten nur ca. 9000 Elemente indiziert werden, das kann in dem Tempo dann Wochen oder Monate dauern bis das fertig.
Hat jemand ne Ahnung was die Indizierung so ausbremst?
Sobald ich nicht arbeiten muss schliesse ich alle Programme, das scheint am Tempo aber nichts zu ändern.

Ich habe einen XP Rechner, SP3 und alle Aktualisierungen drauf. AMD 2 X 3000 GH und 2 GB Ram.

Ist nicht das erste mal das WDS auf dem Rechner installiere, ging sonst immer ohne Probleme.


MfG
7
Antworten
6392
Aufrufe
Bluescreen bei Vista 32
Begonnen von HILTI
02. Juni 2009, 09:23:34
Habe seit ein paar wochen ab und zu einen Bluesceen nur ich weiß nicht wieso

Amd Phenom 9500 Quad Core 2.2
Ram 2GB
MSI BOard
Gforce 8600 GT


Fehler :
Problemsignatur:
 Problemereignisname: BlueScreen
 Betriebsystemversion: 6.0.6002.2.2.0.256.1
 Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
 BCCode: 1000007e
 BCP1: C0000005
 BCP2: 20646156
 BCP3: 8719BBC0
 BCP4: 8719B8BC
 OS Version: 6_0_6002
 Service Pack: 2_0
 Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
 C:\Windows\Minidump\Mini060209-01.dmp
 C:\Users\Hilbert\AppData\Local\Temp\WER-158781-0.sysdata.xml
 C:\Users\Hilbert\AppData\Local\Temp\WER7C1.tmp.version.txt


VIelleicht weiß einer von euch was er bedeutet.


VIelen dank im vorraus



-------------

hab die dump datei ausgewertet viuelleicht könnt ihr damit was anfangen.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini060209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: „SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols“
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81e37000 PsLoadedModuleList = 0x81f4ec70
Debug session time: Mon Jun  1 22:50:53.677 2009 (GMT+2)
System Uptime: 0 days 2:18:50.468
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 20646156, 8719bbc0, 8719b8bc}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                  ***
***                                                                  ***
***    Your debugger is not using the correct symbols                ***
***                                                                  ***
***    In order for this command to work properly, your symbol path  ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Your debugger is not using the correct symbols                ***
***                                                                  ***
***    In order for this command to work properly, your symbol path  ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Your debugger is not using the correct symbols                ***
***                                                                  ***
***    In order for this command to work properly, your symbol path  ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+4b4090 )

Followup: MachineOwner
---------

0: kd> „!analyze -v“
      ^ Syntax error in '„!analyze -v“'
0: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 20646156, The address that the exception occurred at
Arg3: 8719bbc0, Exception Record Address
Arg4: 8719b8bc, Context Record Address

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                  ***
***                                                                  ***
***    Your debugger is not using the correct symbols                ***
***                                                                  ***
***    In order for this command to work properly, your symbol path  ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Your debugger is not using the correct symbols                ***
***                                                                  ***
***    In order for this command to work properly, your symbol path  ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Your debugger is not using the correct symbols                ***
***                                                                  ***
***    In order for this command to work properly, your symbol path  ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT: 
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 81e37000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  49fa9243

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
+3eefe
20646156 ??              ???

EXCEPTION_RECORD:  8719bbc0 -- (.exr 0xffffffff8719bbc0)
ExceptionAddress: 20646156
  ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
  Parameter[0]: 00000008
  Parameter[1]: 20646156
Attempt to execute non-executable address 20646156

CONTEXT:  8719b8bc -- (.cxr 0xffffffff8719b8bc)
eax=8719bca4 ebx=93881750 ecx=20646156 edx=8eabe070 esi=00000000 edi=93872ab0
eip=20646156 esp=8719bc88 ebp=8719bca8 iopl=0        nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            efl=00010246
20646156 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8eabe090 to 20646156

STACK_TEXT: 
WARNING: Frame IP not in any known module. Following frames may be wrong.
8719bc84 8eabe090 93881750 93872ab0 8719bca4 0x20646156
8719bca8 8e79ca1e 93881750 93872ab0 8719bcd8 nvlddmkm+0x4b4090
8719bd08 8e79d2c0 84de4730 81f3913c 8719bd2c nvlddmkm+0x192a1e
8719bd18 8e704803 00000000 98856b70 85b4ef38 nvlddmkm+0x1932c0
8719bd2c 8204486f 85b4ef38 84de4730 846fd8b0 nvlddmkm+0xfa803
8719bd44 81edce22 846fd8b0 00000000 83993d78 nt+0x20d86f
8719bd7c 8200cc42 846fd8b0 9e36b428 00000000 nt+0xa5e22
8719bdc0 81e75efe 81edcd25 00000001 00000000 nt+0x1d5c42
00000000 00000000 00000000 00000000 00000000 nt+0x3eefe


FOLLOWUP_IP:
nvlddmkm+4b4090
8eabe090 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvlddmkm+4b4090

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xffffffff8719b8bc ; kb

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------
21
Antworten
14280
Aufrufe
Arcor DSLwlan modem 200!!!!!!!
Begonnen von selwol
21. Oktober 2008, 21:25:06
« 1 2
Hi, please can someone help,

i have vista premium and the above mentioned router my prob is over wlan is everything perfect but over Lan cable the conection is slow and breaks off very often.

Please help,with XP it was working with no problems.

Sorry for the english but my writen German is not so Good,but you may answer in German.

Danke in voraus

Mark
3
Antworten
5331
Aufrufe
Bei ReadyBoost verlangsamt sich Datentransfer um fast 50% ! Warum?
Begonnen von andreas526
09. August 2008, 15:35:17
:wink Hallo Leute!
Kann mir vielleicht jemand einen plausiblen Grund sagen, warum wenn ich per USB-Stick ReadyBoost aktiviere mein Datentransfer um fast mehr als 50% zurückgeht? An und für sich sollte es ja das System beschleunigen, oder?
Ein Beispiel: Wenn ich zb. meine Dokumente und/oder Downloads auf meine Externe kopieren möchte (ohne ReadyBoost) , zeigt er mir vorerst einmal für ca 10 sekunden ein Datentransfervolumen von 40-50MB/sec an welches dann so nach und nach zwischen 17 und 20 MB/sec stehen bleibt. Das gleiche mit ReadyBoost: Da habe ich von Beginn an schon nur 17-20 MB/sec und geht dann oft bis zu nur 4-7 MB pro sekunde runter!
Meiner Meinung nach läuft da irgendetwas falsch.
Kann es sein, das "RB" nur fürs Betriebssystem gilt und mit Datentransfer nichts zu tun hat?, was ich mir eigentlich nicht vorstellen kann. Wie immer wäre ich über ein paar Kommentare sehr dankbar, Grüße nach Deutschland, Andreas
17
Antworten
19107
Aufrufe
Recovery CD Windows Vista
Begonnen von Steffchen
14. Juli 2008, 11:19:06
« 1 2
Hallo!!!

Ich habe ein Problem...
Und zwar habe ich mir im März 2007 einen Toshiba Läppi gekauft auf dem Vista vorinstalliert war. Ich bin aber nicht damit zurecht gekommen und etliche Proggis liefen nicht darauf und habe deswegen durch einen Bekannten XP installieren lassen.
So nun möchte ich aber doch gerne wieder Vista haben :D.
Im Lieferumfang meinen NB waren lediglich eine Upgrade CD für Vista und eine Recovery CD.
Meine Frage ist nun, ob ich mit der Recovery CD wieder Vista auf dem Läppi habe oder nicht?!
Ich selber habe wenig Ahnung von PC leider leider und wäre sehr froh, wenn mir jemand (verständlich) erklären könnte ob das geht und wenn ja was ich beachten muss....

Danke euch  :))
5
Antworten
20495
Aufrufe
PDF2Word bzw. PDF zu RTF - kostenloses Tool - PDF in Word umwandeln
Begonnen von markus
07. Juli 2008, 18:54:06
Hi!

Bin jetzt schon ewig auf der Suche aber ich finde einfach nix.

Ich suche ein kostenloses Programm, mit dem man aus einer PDF-Datei ein Word-Dokument  (.DOC oder .RTF) erstellen kann (dabei sollte die Formatierung inkl. Bilder natürlich erhalten bleiben).
Ich finde allerdings nichts kostenloses - vielleicht kennt ja jemand eines...
29
Antworten
17238
Aufrufe
CRYSIS -Sammelthread
Begonnen von Gagamel6575
31. Oktober 2007, 22:02:42
« 1 2
Hey ho

Es ist endlich so vom am 16.November erscheinenden Ego-Shooter Crysis gibts erstmals ein Demo.

[url=http://www.crysisdemo.com/]http://www.crysisdemo.com/[/url]

Cheers