Dak

you two are aware that it sounds like your making love, right?

I gotta gmail invite you could have if you wanna temporary fix. you could redirect your mail to a gmail or hotmail account till they sort it out, i suppose.

maybe because the sunglasses prevent our ability to tell wether someone is looking at us or not, it makes it harder for us to guage their level of dominance/submissiveness, and makes them seem like they dont have a position on the 'pecking order' of society by being neither dominant to us nor submissive nor equal, sort of like the 'lone-male' you get in monkey-world, or something? maybe theyre just copying the cool guys in films? role-emulation type-jobby?

did you check out the google search i linked to... yahoo have a history of slow-down in the months following a default storage-space increase.

firewalls and (to my knowledge) avast don't have anything to do with cookies. google seems quite a few people are complaining about yahoo being slow (those results are from the last three months) have yahoo just increased their storage space? they seem to have had problems with slow-down following storage-space upgrades in the past.

i would assume that it depends on how the divorse was handled -- it would surely be better to grow up in a slightly dysfunctional family than in a family that goes through a messy divorse (and conversly, better a clean divorse than a highly disfunctional family)

how bizzare... i was just on my way to ask a similar thing. how do you attach images? i get the image tags... simply type in ; so, for example, right click on the SFN icon and select 'copy image location' now, paste the 'image location' in a post to get http://www.scienceforums.net/forums/images/misc/vbulletin3_logo_white.gif now, whack that address inbetween the img tags, eg: http://www.scienceforums.net/forums/images/misc/vbulletin3_logo_white.gif[/img] to get but how do we attach images (ie, show images which arent on the web and so dont have a web url?

BUMP! is anyone interested in continuing this? (if not, i wont bump it again).

Iv been having the same problem with hotmail, although i have notised that firefox has been playing up in general lately, since roughly the time of the 1.0.4 upgrade.

so which bit does the dual layer core prosesser have two of? (the ALU?)

I believe its phosphoric acid in coke, and apparently liniar alkylbenzine sulfonates1, with the generic equasion R1(CHR2)-PhSO3-Na+ in washing up liquids 2 (pdf) sooooooooo... I assume that youd get a mixture of H2PO4-Na+, HPO42-Na22+, and PO43-Na33+ salts , and R1(CHR2)-PhSO3H. with sodium dihydrogen phosphate being the resulting salt in the 'bit of detergent left in glass of coke' example above, due to the exess of phosphoric acid compared to liniar alkylbenzyl sulfonate. maybe. btw, i came across this (pdf) info, related to the toxicity of fairy liquid (a common washing up liquid in the UK).

10 have said yes. two have 'had difficulties'. as long as at least 10 of the remaining 13 vote yes, its possible that the constitution could be forsed through, or the contries that voted no would have another referendum.

umm... what else does a prosesser do? I thought that it just calculated?

Are you telling me that you could neck an intire bottle of fairy, and the only adverse effects would be the squits??? That'd be some interesting dihoreahh... I wonder if it would bubble?

logically speaking, no: if detergent was toxic enough to be harmful at very small doses, its doubtful that the companies would be legally alowed to sell it for the purposes of cleaning eating utensils. actually, i wouldnt be surprised if the coke was more harmful than the detergent.

whats hyperthreading? and are two 1G prosessers better than one 2G prosesser? what about, are two 32bit prosessers better than one 64bit prosesser? and whats the prosessers 'core'? you have piqued my interest!

How do you use the quote button? actually, the new buttons (including the lighter colour) are already growing on me, and they do stand out so that their easyer to find/use. [edit] nice 'this forum has/does not have new posts button[/edit]

your right. sugars that are in their liniar form, for example, would be Cn(H2O)n+1; however, the vast majority of hydrocarbons carbohydrates are of the formula Cn(H2O)n IIRC (?)

have emailed you the screen-shots. also, thought id mention that the problem goes away if i select 'SFN vbulletin 3 style' (ie, the old one)

here you go: btw, how do you get the image to actually display on the post? (it already has tags around it )

yeah, id agree - i liked the old padlock for a locked thread, although the roundness looks better. how about the old symbles and colour but in a rounded box?

ultimately, people will be the best tool, as people are actually more versatile than programs in interpreting code. for example, if you right-click on this page and select 'view source code/view page source', you get the XHTML code for this page. if any part of this code becomes corrupted, it runs the risk of the file, or part of the file, not being readable by a programme. take this bit for illustration of my point: .tcat a:hover, .tcat a:active { color: #FFFF66; text-decoration: underline; } say it gets randomly corrupted, and the 'x' of text is deleted, giving .tcat a:hover, .tcat a:active { color: #FFFF66; tet-decoration: underline; } now, as 'tet-decoration' isnt a valid XHTML value, the web-browser which is reading it wont understand the variable which follows, and so will not do anything with that entire line of code (in this case, umm, lesse, i believe that the code means that when the curser is plased over the link, that it should change colour to whatever colour #FFFF66 is, and also should become underlined. the deletion of the x means either that the link will change colour but not become underlined, or that entire segment of code will become unreadable and so nothing will happen when the cursor is put over the link) a human, however, can look at the line 'tet-decoration: underline;' and understand what it means, and even fix it by inserting the missing x. thats why humans are the most inportant tool. a slightly better example could be this: <!-- post #173863 --> <!-- open content container --> <div align="center"> <div class="page" style="width:100%; text-align:left"> <div style="padding:0px 15px 0px 15px"> <div style="padding:0px 0px 6px 0px"> <table class="tborder" cellpadding="6" cellspacing="0" border="0" width="100%" align="center"> <tr> <td class="thead" style="font-weight:normal" > <!-- status icon and date --> <a name="post173863"><img class="inlineimg" src="http://www.scienceforums.net/forums/images/statusicon/post_old.gif" alt="Old" border="0" /></a> Yesterday, 03:38 PM <!-- / status icon and date --> </td> <td class="thead" style="font-weight:normal" align="right"> <!-- checks for warning system --> <!-- end of warning system --> #<a href="showpost.php?p=173863&postcount=2" target="new"><strong>2</strong></a> </td> </tr> <tr valign="top"> <td class="alt2" width="175"> <div id="postmenu_173863"> <a class="bigusername" href="member.php?u=1747">5614</a> <script type="text/javascript"> vbmenu_register("postmenu_173863", true); </script> </div> <div class="smallfont">Scientist</div> <div class="smallfont"> <br /><a href="member.php?u=1747"><img src="image.php?u=1747&dateline=1115977451" alt="5614's Avatar" border="0" /></a> </div> <div class="smallfont"> <br /> <div><span style="font-style: italic;">Join Date:</span> Jun 2004</div> <div><span style="font-style: italic;">Location:</span> London, UK</div> <div> <span style="font-style: italic;">Posts:</span> 3,304 </div> <div style="padding-top: 5px;"> <a href="#" onclick="return imwindow('aim', '1747', 400, 200)"><img src="http://www.scienceforums.net/forums/images/misc/im_aim.gif" alt="Send a message via AIM to 5614" border="0" /></a> <a href="#" onclick="return imwindow('msn', '1747', 400, 200)"><img src="http://www.scienceforums.net/forums/images/misc/im_msn.gif" alt="Send a message via MSN to 5614" border="0" /></a> </div> </div> </td> <td class="alt1"> <TABLE width=100%><TR> <TD width=90%> </td> <TD width=10% align="right"> </td> </tr></table> <hr size="1" style="color:#C1C1D1" /> <!-- message --> <div>What do you want to do? <i>It's not clear</i>. Do you want to search a suspect computer for possible evidence? Do you have it in front of you, or are you doing this remotely?<br /> <br /> In any case special software is used, the public can normally get similar things, although the best quality is stuff is either expensive or not available to the public.</div> <!-- / message --> <!-- sig --> <div> which i believe is the first part of the coding to display this post by 4nums. now, if im reading this right (and its entirely possible that im not, what with not being able to read XHTML and what not, but here goes) i believe that a corruption the second line of code (ie: <!-- open content container --> ) would render that entire bit of code incomprehensible to a computer programe as the interpretation of everything that follows is dependant on knowing that it should be in a content container (possibly). however, everything that follows is still understandable by a human reading the source code, most notably the last bit, <!-- message --> <div>What do you want to do? <i>It's not clear</i>. Do you want to search a suspect computer for possible evidence? Do you have it in front of you, or are you doing this remotely?<br /> <br /> In any case special software is used, the public can normally get similar things, although the best quality is stuff is either expensive or not available to the public.</div> <!-- / message --> <!-- sig --> <div> which means that his mesage can still be read, even though the code that precedes it might be shafted to the point that a programe could not read anything past that point. or something. i cant code myself, so feel free to correct any errors.

if you mean what i think you mean, then i believe it is vaguely similar to how the tags on this forum work. so, the data is written in thus format (although obviously in binary): [file=C:\user\bob\desktop\shopping_list]01110101001101010110[/file] if its fragmented, id assume its: [file=C:\user\bob\desktop\shopping_list.txt]0111010100[fragmented:goto disk location blah][/file] then at location 'blah', there would be [file=FRAG2.C:\user\bob\desktop\shopping_list.txt]1101010110[/file] and if the file [file=C:\user\bob\desktop\shopping_list.txt]01110101001101010110[/file] is deleted, it becomes [delete][file=C:\user\bob\desktop\shopping_list.txt]01110101001101010110[/file][/delete] in which case new data can be written over it. that may be a tad incorrect, but its vaguely how it works. forensically, a program is used which displayes the sourse code rater than interpreting it like windows does (ie, windows will completely ignoor something in the [delete]tags, but the code-viewing software will still display the code -- id assume a simple copying of the data, removing the delete tags and saving it to disk then viewing with the appropriate program (and obviously locating all of the file fragments) will allow retrieval of the data.

also, the disk 'wobbles' as it is reading/righting. ok, imagine that this is the lense x x x <-- chunky lense x x x right, as the lense goes along, it rights traxs of data, much like youd get on an LP, but of course in binary (ie, the disk is round and the data is written in spirals). below is an example of a line of binary data, written by that chunky lense shown above. Note that the lines are repeated to represent the size of the line of data (not that the 0s and 1s are repeated six times -- that would just be silly) 00010110111001x 00010110111001x 00010110111001x<-- chunky lense wrighting data 00010110111001x 00010110111001x 00010110111001x now, imajine that the data is deleted and written over. because the disk 'wobbles' as it is in use, the lense may not be alighned 100% accurately over the line of data, so it will over-right most, but not all, of the data like so: 01011010101110x 01011010101110x 01011010101110x<--chunky lense wrighting data 01011010101110x 01011010101110x 01011010101110x 00010110111001 <---------remenant of previouse data. now we get this: 01011010101110 01011010101110 01011010101110 01011010101110 01011010101110 01011010101110 00010110111001 notice how, due to the wobble, theire are essentially two lines of data here - the larger new line (a single bit of info from this line is shown in blue above), and the smaller older line of data (one bit of info picked out in green above) noooow, when the lense comes to reading the data it can 'wobble' again and read both data streams like thus: 01011010101110 01011010101110x 01011010101110x<--chunky lense reading data data 01011010101110x 01011010101110x 01011010101110x 00010110111001x which isnt actually a problem. the last bit of data that it reads (shown above in red) is predominantly '0', and only a little bit '1', so the chunky lense doesnt even notice the '1' from the old data; the bit is read as a '0' and everything works ok. forensicly, it is possible to put the disk from the hdd into another hdd with a smaller lense, for example x <-- small lense. this forensic hdd is well made and runs at a slow speed, to minimise wobble. now, when the disk is read, the area looked at is much smaller (shown in blue): 01011010101110x <--thin lense reading 01011010101110 01011010101110 01011010101110 01011010101110 01011010101110 00010110111001 in the above example, the lense would read '01011010101110', which is the new data -- nothing spesial there. on the next pass, it would read another thin sextion of the line of data. eg: 01011010101110 01011010101110x <--thin lense reading 01011010101110 01011010101110 01011010101110 01011010101110 00010110111001 again, the lense would read '01011010101110', which is still the new data -- so still nothing spesial there. eventually, the lense would read the bottom part of the line of data like thus 01011010101110 01011010101110 01011010101110 01011010101110 01011010101110 01011010101110 00010110111001x <--thin lense reading now the lense reads '00010110111001', which is the old data that had been deleted and written over. ta da! deleted and over-written data retrieved. sorry if that was a tad long-winded.