高手帮我来分析分析这段css 样式 谢谢了

Posted 2023-02-16

我要做论坛,但小弟的CSS样式很一般.有哪为高手指点一下.最好给我几个教程.我把我的积分都献了.谢了`!
我只要知道那些样式是干什么的.怎么改.不是要套用别人的.

body font-family: Verdana;FONT-SIZE: 12px;MARGIN: 0;color: #000000;background: #ffffff;
td FONT-SIZE: 12px;
textarea,input,select
font-family: Verdana;
font-size: 12px;
background-color: #ffffff;

formmargin:0px; display:inline
div.quotemargin:5px 20px;border:1px solid $tablecolor;padding:5px;background:$forumcolorone;line-height : normal;
a TEXT-DECORATION: none;
a:hover text-decoration: underline;
img border:0;
.bannerbackground: #84AACE;
.imglogo
MARGIN: 0px;
padding: 0px;
TEXT-ALIGN: center;
background-color:#84AACE;
background-image:url(http://bbs.lunqun.com/image/lunqun/logo.gif);
WIDTH: 295px;
HEIGHT:87px;

.head color: #FFFFFF;background: #84AACE;padding: 5px;font-weight:bold;
.head acolor: #FFFFFF;
.f_one background: $forumcolorone;
.f_two background: $forumcolortwo;
.hr border-top: 1px solid $tablecolor; border-bottom: 0; border-left: 0; border-right: 0;
.t_one background: $threadcolorone;
.t_two background: $threadcolortwo;
.r_one background: $readcolorone;
.r_two background: $readcolortwo;
.cbg color:#000000;background: #E5E8EA;
.cbg a color:#000000;
.smalltxt font-family: Tahoma, Verdana; font-size: 12px;
.tinytxt font-family: Tahoma, Verdana; font-size: 11px;
.cfont color:#FFFFFF;
.fnamecolor color:#003366;
.index_fontcolor: #3A4F6C;background-color:#E5E8EA; font-weight:bold;padding: 5px;
.tpc_title font-size: 12px;font-weight:bold;
.tpc_content font-size: 13px;
.i_table BORDER: $tablecolor 1px solid;background:#D6E3EF;
.tool color:#84AACE;
.menuposition:absolute; 参考技术A 别人给你改点恶意代码怎么办？
百度有说明的
只要你有点电脑知识就可以

百度空间那有
完了你进去对照改
保存之前点预览

直到自己满意 参考技术B http://www.tblog.com.cn
我收藏了这个人博客
里面有一个连载的文单写的非不错
关于CSS+DIV的...建议楼主去看看...会很有收获的 参考技术C 我不知道你要什么样的分析。不过http://www.chinaddu.com/tutorial/homepage/css/index.html
这个地方有很多实用的教程。你自己看下有没有需要的东西 参考技术D 把网页打上让我们看看。 第5个回答  2006-08-08 什么啊 说清楚点啊

请高手帮我分析下Minidump文件，如果真确定有重酬

具体内容在下面1楼

全文是如下：（这个不是答案而是用户提问的内容，请高手显身）

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

Loading Dump File [%SystemRoot%\Minidump\Mini061409-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 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 XP Kernel Version 2600 (Service Pack 3.3300) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Sun Jun 14 01:59:47.156 2009 (GMT+8)
System Uptime: 0 days 11:50:22.961
*********************************************************************
* 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 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 1000008E, c0000005, 8052f787, b690bc80, 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+57787 )

Followup: MachineOwner
--------- 参考技术A 楼主，重新安装系统吧，windows系统内核错误，无法解决 参考技术B 高手显身：如此这般，这般如此，哇哈哈，呀呼嘿