Win98SE Install Datum

Dieses Thema Win98SE Install Datum im Forum "Windows 95-2000" wurde erstellt von MasterJM, 5. Dez. 2002.

Thema: Win98SE Install Datum Hi, ich würde gerne das Datum einer Win98SE Installation nachgucken. Sprich wie alt das Win ist. Durchsuche grad...

  1. Hi, ich würde gerne das Datum einer Win98SE
    Installation nachgucken.

    Sprich wie alt das Win ist.

    Durchsuche grad Reg finde aber soch richtig nichts,
    jemand einen Tipp?

    thx :)
     
  2. Das Erstellungsdatum vom Windows-Ordner !?
    Windows protokolliert seine Geburt nicht sonderlich gut.

    Dirk
     

  3. hm ne das wäre zu unsicher, ich kann mich dran erinnern
    früher mal ein mIRC script gehabt zu haben,
    was z.b. die Wochen/Tage seit Install des OS gezählt hat.

    Das muss die Daten ja irgendwo aus der Reg (oder so)
    gehabt haben.

    Leider finde ich auch dieses Script nicht mehr auf meiner Platte.
    :)
     
  4. Hallo,
    ich kann mich der Meinung meiner beiden Vorgänger nur anschließen, bei zeigt der Windows Ordner noch genau das Datum der Neuinstallation des letzten Monats an...
     
  5. Hmm...
    Wenn ich nicht irre, legt W9x eine Datei auf dem Systemlaufwerk an, die 1stboot o.ä. heisst - diese wird beim ersten Booten des Systems erstellt, wie der Name ja schon sagt.

    Besagtes mIRC-Script tut nix anderes, als das Erstelldatum dieser Datei auszulesen.

    Btw ist dieses Datum das selbe wie das des Ordners, in den Windows installiert wurde.

    Cheers,
    Joshua
     
  6. die Datei ist natürlich sofort gelöscht
    und trotzdem ging das script.


    Das mit dem Ordner Datum mag ja stimmen :)
    funktioniert aber nicht, wenn man ordner moved
    kopiert und den neuen umbennent -> alten löscht ;)

    hm :)
     
  7. das mirc alias dafür leutet btw:

    //say $duration($ticks)

    mal nachforschen, woher mirc die info nimmt ;)
     
  8. Jetzt hab ich was gefunden:

    machine.PNF
    im INF Ordner,
    daraus kann man die ctime seit dem install auslesen

    Passt bei mir genau.

    :)
     
  9. START>Ausführen>msinfo32

    ...müsste eigentlich auch das Datum aus der Registry
    bzw. hwinfo.dat auslesen.

    *.PNF Datein werden bei jeder (Treiber)Installation neu erzeugt.(=alte *.INF)

    Sind also Datenmüll, den man eigentlich löschen kann.

    fG
    @thehop
     
  10. Hey Leute,

    hab gerade Win 7 Professional 64bit installiert (final von der Uni) . Hat alles wunderbar funktioniert. Nur kam jetzt schon 2mal ein Bluescreen und der PC hat neugestartet.

    Hab mit windbg mal die Crash-Dumps ausgelesen und kam folgendes herraus:


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


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

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02603000 PsLoadedModuleList = 0xfffff800`02840e50
    Debug session time: Fri Sep 11 18:55:00.254 2009 (GMT+2)
    System Uptime: 0 days 0:10:25.971
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c0000005, fffff8000291e0fa, fffff88008f930d0, 0}

    ***** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : ntoskrnl.exe ( nt+31b0fa )

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



    --> Probably caused by : ntoskrnl.exe ( nt+31b0fa )

    sagt das jemandem was? Wodran könnte das liegen und wie kann ich das vll. lösen?

    Hoffe Jemand kann mir helfen.

    Danke schonmal,
    Nemaides
     
Die Seite wird geladen...

Win98SE Install Datum - Ähnliche Themen

Forum Datum
Win98SE - Abgebrochene Drüberinstallation rückgängig machen. Möglich? Windows XP Forum 26. Jan. 2007
Neuinstallation von Win98SE Windows 95-2000 10. Nov. 2004
Win98SE neu installiert = wie IE-5.0 auf 5.5 updaten ? Sonstiges rund ums Internet 25. Okt. 2004
winme lässt sich nicht auf win98se installieren... Windows 95-2000 13. Sep. 2003
Neues Board in bestehende Win98SE Installation Windows 95-2000 22. Aug. 2003