Audi_Roy

Medlemmer
  • Innholdsteller

    13
  • Ble med

  • Besøkte siden sist


Nettsamfunnsomdømme

0 ProPoeng

Om Audi_Roy

  • Rang
    Nyansatt

Min datamaskin

  • Operativsystem unkw

Audi_Roy sin aktivitet

  1. Audi_Roy la til et innlegg i et emne Port 80 redirect   

    Hei igjenn..

    Ok, det var toskete. .. Håpet en ala webserver kunne styre dette, da både subsonic og NAS krever port 80
    • 0
  2. Audi_Roy la til et emne i Webutvikling   

    Port 80 redirect
    Hei.

    Beklager om denne posten havner feil, men fant liksom ikke helt ut hvor jeg skulle legge den.

    Lurer på følgende problem:

    har en egen musikkserver stående, som kjører subsonic gjennom port 80.
    Så har jeg en NAS disk som også kjører på port 80.

    Er det noen mulighet å f.eks: ved å skrive "min no-ip adresse" kommer man til en webside med valg for f.eks Musikk eller NAS, osv..?

    Problemet slik som det er nå, er at når begge er "aktiv" så blir NAS foretrukket.

    Håper dere skjønner:)
    • 2 svar
    • visninger
  3. Audi_Roy la til et innlegg i et emne [LØST] Forslag for domene.   



    www.datatinget.com

    www.datating.com

    www.divdata.com

    www.datasaker.com

    etc..
    • 0
  4. Audi_Roy la til et innlegg i et emne [LØST] Lese dump filer   

    Da er det på tide å oppdatere tråden og sette den som løst, da maskinen har snurret i dagevis uten blåskjerm..

    Var antagelig bare noe "smuss" på driverne

    Mvh
    • 0
  5. Audi_Roy la til et innlegg i et emne Brannmurprogram og spywareprogram?   

    Hei.

    Om du vil betale noen kroner for noe bra, vil jeg anbefale ESET Smart Security ( http://www.eset.com ) ..

    Funker meget bra med Win 7..


    Mvh
    • 0
  6. Audi_Roy la til et innlegg i et emne [LØST] windows 7 dual boot   



    Et lite tips:

    Last ned Neosmart EasyBCD - http://neosmart.net/dl.php?id=1

    Der skal du få opp alle OS som er installert og skal da kan velge hvordan som skal prioriteres, og sette timer på de..


    Mvh
    • 0
  7. Audi_Roy la til et innlegg i et emne [LØST] Lese dump filer   


    Hei.

    Takker for den:)

    Da sliter jeg litt, da jeg har prøvd legge inn de siste driverne til ATI kortet, som desverre ikke er kompatibelt med Win 7.. Enda..

    Men da får jeg bare se hvordan dette går da:=)

    Mvh
    • 0
  8. Audi_Roy la til et innlegg i et emne [LØST] Lese dump filer   


    Hei.

    Ja, hadde jo ikke forventet noe annet egentlig, men kjørte jo beta i lang tid uten problemer..

    Men her er linkene til dumpfilene...:

    http://s1.filesdump.com/file/a747647ea91c/mini1.dmp.html

    http://s3.filesdump.com/file/e77e1842a1c9/mini2.dmp.html

    Mvh
    • 0
  9. Audi_Roy la til et emne i Windows   

    [LØST] Lese dump filer
    Hei.

    For det første. så var jeg litt usikker på hvor denne tråden skulle plaseres, men da OS gjelder Win 7 håper jeg den er på rett plass:)

    Problem:

    Har hatt 2 blue-screen siden jeg la inn RC utgaven, og da er det generert dump filer, men får ikke til å lese ut av de..

    Har lastet den WinDebugg og symbols, men klarer ikke få dette til å passe sammen..

    Er det noen her som ev kan lese ut av dumpfilene? Har kjørt XP fast og stødig uten noe BS, så lurer på om det kan være noe driverkluss.

    Men legger med det som jeg får opp i de 2 filene, så kan noen se om det er rett:


    Dump 1 - 050609-21140-01.dmp (klikk for å vise/skjule) Microsoft ® Windows Debugger Version 6.11.0001.404 X86
    Copyright © Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\mini2.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`80d8ada4?
    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
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0x82804000 PsLoadedModuleList = 0x82943570
    Debug session time: Wed May 6 17:45:12.307 2009 (GMT+2)
    System Uptime: 0 days 11:25:10.367
    *********************************************************************
    * 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
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ....




    Dump 2 - 050609-26359-01.dmp (klikk for å vise/skjule) Microsoft ® Windows Debugger Version 6.11.0001.404 X86
    Copyright © Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\mini1.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
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0x8280a000 PsLoadedModuleList = 0x82949570
    Debug session time: Wed May 6 21:57:54.861 2009 (GMT+2)
    System Uptime: 0 days 0:02:10.783
    *********************************************************************
    * 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
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** 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 D1, {80917fb8, 2, 0, 80917fb8}

    *** WARNING: Unable to verify timestamp for dxgmms1.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    ***** 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 : dxgmms1.sys ( dxgmms1+b01d )

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



    Er det noe skikkelig galt her?

    Håper på kjappe svar/tips


    Mvh
    • 5 svar
    • visninger
  10. Audi_Roy la til et innlegg i et emne [LØST] Fjerne Win 7 fra bootmeny   


    Hei.

    Som nevnt i føste post, editerte jeg den med løsning, som var å bruke EasyBCD. Eneste programmet som leste inn bootmenyen slik den var..

    I msconfig slettet jeg alt som hadde med win7 å gjøre, og laget den slik den skulle være, men uten hell..

    Mvh

    -{Audi_Roy}-
    • 0
  11. Audi_Roy la til et innlegg i et emne [LØST] Fjerne Win 7 fra bootmeny   


    Hei.

    Nei, det gikk ikke.. Prøvde alt via msconfig, men uten hell..
    Under bootmeny kom det opp 4 valg;

    Eldre versjon av Windows
    Windows 7
    Windows 7 Recovery
    og

    Memory Diagnose ( litt usikker hva som står direkte )

    Og i msconfig kom ikke de opp, men i EasyBCD kom alt opp slik slik at det var bare å sette XP som hoved OS og slette de andre..
    • 0
  12. Audi_Roy la til et emne i Windows   

    [LØST] Fjerne Win 7 fra bootmeny
    Hei.

    Etter mye prøving, feiling, testing og lesing, ser jeg ingen andre løsninger enn å spørre dere her inne om litt hjelp:

    Som overskrifta sier, så har jeg hatt win 7 installert på en annen disk (D:) og kjører Xp Home på C: .

    Men nå er D: formatert og bruker kun Xp, men ved oppstart kommer bootmenyen frem, og med Win 7 som førstevalg.

    Har redigert boot.ini fila, og den ser slik ut: ( Ligger i root c: )



    C:\BOOT.INI (klikk for å vise/skjule) ;
    ;Warning: Boot.ini is used on Windows XP and earlier operating systems.
    ;Warning: Use BCDEDIT.exe to modify Windows Vista boot options.
    ;
    [boot loader]
    [operating systems]
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /NOEXECUTE=OPTIN /FASTDETECT


    Og her er den i C:\windows :


    C:\WINDOWS\BOOT.INI (klikk for å vise/skjule) [boot loader]
    timeout=0
    default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

    [operation system]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="
    Microsoft Windows XP Home Edition" /fastdetect


    Er det noen av dere som kan se hva som er feil egenlig?


    Mvh

    EDIT:

    Problem løst med Neosmart EasyBCD.. Lastet ned fra: http://neosmart.net/dl.php?id=1 ..

    Der fikk jeg opp alt, så var det bare å redigere og slette det som ikke passet:)
    • 4 svar
    • visninger
  13. Audi_Roy la til et innlegg i et emne Generell diskusjon om Windows 7   

    Heihei.

    Ønsker meg selv velkommen til forumet og benytter da annledningen til å komme med inspill/spørsmål om Win 7.

    Har testa det siden Betaen kom ut, og må si at jeg ble positivt overasket.. Men eneste tingen som plager meg, og gjør at jeg enda holder litt igjenn på Xp, er:

    når MSN Live kjøres, og jeg åpner Firefox, og minimerer ruta til FF, så åpner/maksimerer MSN vinduet seg.
    Har ikke sett noen andre som har vært borti dette, så begynner jo å lure om det er kun jeg som har dette problemet?

    Håper dere kan dele deres meninger og tips:)


    Mvh

    EDIT:

    Fant en link til en side, som kanskje kan være til nytte.. Om noen kunne testet denne,og gitt tilbakemelding, hadde det vært knall:)

    Hov to minimize MSN to systray: http://windows7center.com/windows-7-tips/h...y-in-windows-7/
    • 0