bristols
Content Type
Profiles
Forums
Events
Posts posted by bristols
-
-
How do I apply that css code though? I'm not sure I'm doing this right...
here is my code so far.
<html>
First things first - to avoid variations in how your page displays across different browsers, every HTML page you create should start with something called a DOCTYPE. A DOCTYPE just tells the browser that it should expect your page's code to be written according to a certain standard. See, not all HTML is the same - at least, it can be written according to different standards. There's more than one standard of HTML, and so there are a number of different DOCTYPEs to match. Use a search engine to search for "html doctypes". Below, I've chosen a Transitional DOCTYPE that hopefully will suit your needs. The 'DOCTYPE declaration' should be the first line of HTML code for each of your pages, coming before even the HTML element:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">Actually this is an XHTML DOCTYPE. When using this kind of DOCTYPE the HTML element should look like this:
<html xmlns="http://www.w3.org/1999/xhtml">rather than just
<html>saved in to a text document, named stylesheet.txt
Whoa there - CSS files must end with the .css file extension, not .txt or anything else. Save your stylesheet.txt file as a CSS file, so that it's called stylesheet.css instead.
OK, below is the code for your example HTML file, and it's accompanying CSS file. Hopefully it solves your problem. (By the way, I've added some filler content to the HTML):
HTML file
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title> removed for forum purposes </title>
<meta name="description" content="removed for forum purposes" />
<meta name="keywords" content="removed for forum purposes" />
<meta name="robots" content="index, follow" />
<meta name="revisit-after" content="2 month" />
<link rel="stylesheet" type="text/css" href="stylesheet.css" />
<style type="text/css">
</style>
</head>
<body>
<div id="wrapper">
<p>blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... </p>
<p>blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... </p>
<p>blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... blah blah here's some content... </p>
</div>
</body>
</html>CSS file
*{
margin:0;
padding:0;
}
body{
text-align:center; /*For IE6 Shenanigans*/
}
#wrapper{
width:960px;
margin:0 auto;
text-align:left;
}Note that the link in the head part of the HTML to your CSS file has been updated to reflect the fact that your CSS file should end with the .css file extension.
0 -
You must have (IE6) installed.
Pity.
Why, exactly?
0 -
I thought MSXML 4.0 SP2 supersede older versions. If it doesn't then I can add'em all.
I'm pretty sure that, just like .NET Framework, it doesn't. Occasionally there might be some app or other that requires Msxml.dll rather than Msxml2.dll, for example.
My opinion: make all MSXML versions apart from 2.5 SP3 optional. As I said, 2.5 SP3 is an update for the version that shipped with 98 SE.
0 -
I'm going to add MSXML 4.0 SP 2, are there an objections?
Have you added MSXML 2.5?
Windows 98 SE shipped with MSXML 2.0b (Msxml.dll). MSXML 2.5 SP3 (direct download) was the last version that retained that file name (build 8.00.6730.0). MSXML 2.6 was Msxml2.dll, version 3 was Msxml3.dll, and so on.
0 -
I noticed that your W2KSP4 updates list doesn't have Windows2000-KB977377-x86-ENU.EXE (Schannel.dll, 5.1.2195.7371).
Instead, it's present Windows2000-KB960225-x86-ENU.EXE (Schannel.dll, 5.1.2195.7213).
Am I wrong?
No, you're right.
As I remember it, 977377 was somewhat buggy, breaking TLS. The KB article lists several known issues (but also a registry workaround). XP got subsequent updates that fixed the issues 977377 caused, but unfortunately Windows 2000 did not.
I could list it. So far I have not, since I remember people being unhappy with it at the time that it was released, and I seem to remember also that the update was recommended for server admins and not end users. Blackwingcat also removed the update from his SP5 list.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
4 November 2011
Added: updates
- Added 826127 (hotfix available by request). Thanks blackwingcat (translated from Japanese to English via Google Translate).
- Added 983234 (hotfix available by request).
- Added Services (assigned port numbers) update (unofficial). Thanks MDGx.
Changelog shows all recent changes.
--------------------
Hi acus
Hi, while I was reading the blog of Blackwingcat, I have noticed that he found a "new" hotfix fo Win2000, related to keyboard driver.
I had already seen that, but thank you for taking the time to post here. Included in today's update.
0 -
The goal is simply to play MP3s stored on the external drive using the host computer.
0 -
I want to allow read-only access in Windows 2000 to an external USB hard drive.
There's a registry setting in Windows XP SP2 that allows this:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\StorageDevicePolicies]
WriteProtect = 1Unfortunately it has no effect in Windows 2000. I know of a setting that disables both write and read access, but that does not serve my purpose (to have read-only access).
The hard drive in question is an IDE drive. It has no physical write-protect switch (neither does the external HDD caddy) and, it seems, it does not allow write protection by configuration of its jumpers. As far as I can tell, the host machine provides no BIOS setting for it, either.
Does anyone know if there is an equivalent registry tweak for Windows 2000 to the one above for Windows XP, or any other method to obtain read-only access? For example, is there some third-party software that will achieve it in Windows 2000? Perhaps there is some universal jumper setting that I'm not aware of. More radically, does anyone know if I can achieve it by modifying the IDE cable and / or blocking the connector pins?
0 -
Not sure whether this would help or not: it would be more of a workaround than a direct fix for any Windows 2000 limitation, and involves using third-party software; but have you tried using USB Drive Letter Manager? It has various configurable settings for hibernation - see the help page.
0 -
the fewer updates, the better
Sure, but that's not the only consideration.
Thanks tomasz86.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
8 October 2011 - 27 October
Added: updates (thanks tomasz86)
- Added 2479628 v9 (unofficial). This new version replaces all previous versions, and is good for those slipstreaming either IE5 or IE6 updates, but it requires that you use HFSLIP 1.7.10 beta J v5 or newer.
- Added 2079403 v2 (unofficial).
- Added Microsoft Remote Desktop Client 5.2 (unofficial).
- Added 906569 (unofficial).
- Added 950305 (unofficial).
- Added 954193 (unofficial).
Added: updates
- Added Root Certificates, updated October 2011.
- Added Adobe Flash Player 11 SWFLASH.CAB, 4 October 2011 release (11.0.1.152) (thanks jvidal). Requires HFSLIP to 1.7.10 beta J v6 (thanks Mimo).
Superseded updates
- 958470 (is superseded by Microsoft Remote Desktop Client 5.2 (unofficial)).
Other changes
- 980232 is not superseded by 2511455. If slipstreaming the latter, you must also include the former (thanks tomasz86).
- Restored 839228 to the Windows list (from the Obsolete list). It contains some latest files for those not using hotfixes by request.
- Updated the folder for 896081 from HF to HFSVCPACK_SW1 (thanks tomasz86).
Removed
- Removed both the IE5-compatible and IE6-only versions of the unofficial 2479628 v7 (both are replaced by 2479628 v9).
- Removed 2079403 (replaced by 2079403 v2).
- Removed Root Certificates Update, June 2011 (replaced by Root Certificates, October 2011).
- Removed Adobe Flash Player SWFLASH.CAB, 21 September 2011 release (10.3.183.10).
Changelog shows all recent changes.
Edit:
Removed 908536 from the updates list because Uxtheme.dll seems to cause problems with .NET Framework-based applications.
0 -
Thanks tomasz86.
Aside from rdbss.sys, did you add anything else to 2511455?
If not, I guess it's OK to continue using 980232 together with the existing 2511455 by WildBill. Is that right?
0 -
I use 1by1 and Quintessential Media Player (QMP). The latest (and perhaps last) version of QMP seems to me to be very stable and tightly-coded, using relatively few resources. It's the sweetest-sounding player for music I've ever used, and has a surprising breadth of features (including MP3 / OGG encoding, for example).
In case QMP interests anyone, they might benefit from adding MP4 and FLAC format support from the input plugins available. There's also an Audioscrobbler plugin for QMP.
0 -
If you're determined enough you can still force Yahoo to show you the classic version. I don't know for how long, but we can hope.
Click on the "help" link in the Upgrade Page text. There is a link in the help page text to stay with Classic.
Perhaps for users of Yahoo Mail in the US; but not for me, at least, who resides outside. I'm still seeing the interstitial upgrade page every time I log in. That page informs me that I have until 07-11-2011 to upgrade. There is no obvious link on the Help page from that interstitial page that offers the option of sticking with Classic.
If anyone could provide such a link I'd love to hear - obviously I'd like to stay with Classic.
0 -
Hi WildBill,
Speaking of MS11-020, it's now posted. I reached the point where if I had to stare at it any longer I'd scream. The critical security patch has been in for a LONG time -- I got a little too ambitious and tried to also shoehorn KB968389 in.
Speaking of shoehorning... Would you consider releasing two kinds of patches for each respective MS update that you work on?:
- a patch that goes no further than to address the issue(s) that the original MS update addressed - that is to say, one that accepts the boundaries of, and tries simply to emulate, the official update
- a patch containing all the extra, more experimental stuff you're exploring here, which has a much wider scope than the original patch
This would allow less technical and/or more time-starved users to continue the journey of keeping their Windows 2000 systems alive, as well as those who might find your more experimental work interesting but have no immediate use for its potential benefits. I think you'd bring along more users of your updates if people had the option to install these 'faithful', more stable updates - it might give them more confidence to try the experimental patches at their leisure. As things stand, users of your patches are obliged to take some extra risk in order to keep their systems up-to-date, since they have to go along your more experimental path with you. In addition, the potential for conflicts between your patches and those made by others (for example, blackwingcat) is now growing, it seems to me.
Speaking for myself, I would like to have this option. I'd like to be able to check out your experimental work when it's more established.
What do you think? Is this unreasonable? Would keeping two separate branches for each update amount to too much extra work?
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
3 October 2011
Added: updates
- Added 954920 v2 (thanks tomasz86).
- Added 960071 v2 (thanks tomasz86).
- Added 2360937 v2 (thanks WildBill).
Removed
- Removed 2360937 (replaced by 2360937 v2).
Changelog shows all recent changes.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
25 September 2011
Added: updates
- 927489 v2 (thanks tomasz86).
- 2616676 v2 (thanks tomasz86).
- Added Adobe Flash Player SWFLASH.CAB, 21 September 2011 release (10.3.183.10) (thanks jvidal).
Removed
- Removed 927489 (replaced by 927489 v2).
- Removed 2524375 (replaced by 2616676 v2).
- Removed Adobe Flash Player SWFLASH.CAB, 25 August 2011 release (10.3.183.7).
Changelog shows all recent changes.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
18 September 2011
Added: updates
- Added 982214 v2 (thanks WildBill).
- Added 927779 v2 (for MDAC 2.81), 2510587 (for Windows Script 5.6), Script 5.8 (for Windows Script 5.8), 927489 (thanks tomasz86).
- Added 839264 (thanks tomasz86).
Other changes
- Updated the advice regarding the choice between Script updates.
- Updated the advice regarding MDAC updates.
Superseded updates
- 927779 (is superseded by 927779 v2).
- 971961 and 981350 (are superseded by 2510587).
Removed
- Removed 982214 (replaced by 982214 v2).
For all changes, please read the Changelog.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
A small update:
Added
- Added Adobe Flash Player SWFLASH.CAB, 25 August 2011 release (10.3.183.7) (thanks jvidal).
Removed
- Removed Adobe Flash Player SWFLASH.CAB, 9 August 2011 release (10.3.183.5).
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
29 August 2011
Added: updates
- Added 901377 and 904765 (thanks tomasz86).
Other changes
- Updated the notes for the Internet Explorer 6 CABs IEW2K_4.CAB and WAB.CAB. Extra steps need to be taken to ensure that all IE6-related files are properly installed (thanks tomasz86).
- Updated the folder for 899591 and 829884 from HF to HFSVCPACK_SW1 (thanks tomasz86).
- Updated the folder for 817855 from HF to HFSVCPACK_SW2 (thanks tomasz86).
Removed
- Removed 819753 (replaced by 901377).
All changes can be found in the Changelog.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
A small update:
Superseded updates
- 979402 is superseded by 2378111 (Windows Media Player 9) (thanks tomasz86)
Other changes
- Updated the notes for 891861 (Update Rollup 1). If your computer has a multi-core or hyperthreading CPU, you’re advised to apply a registry fix, as explained in the KB919521 article.
0 -
Windows 2000 Post-SP4 Updates for HFSLIP
17 July - 23 August 2011
Added: updates
Unofficial updates (thanks blackwingcat and tomasz86):
- 935839-v5a
- 829884
More unofficial updates (thanks tomasz86):
- 2467659 (for Internet Explorer 6)
- 2544521 (for Internet Explorer 6)
- 2378111 (for Windows Media Player 9)
- 2412687
- 2506212
- 2510581 (Script 5.7)
- 2524375
- 2562937
- 2570791
- 961451 (MDAC 2.8 SP1)
- 2419632-v2 (MDAC 2.8 SP1)
- 968006
- 975558
- 2416400 v2 (thanks tomasz86).
Official updates:
- 324178
- 817855 (for Windows Media Player 9)
- Adobe Flash Player SWFLASH.CAB, 9 August 2011 release (10.3.183.5) (thanks jvidal).
Other changes
- Updated the notes for 891861 (Update Rollup 1). If your computer has a multi-core or hyperthreading CPU, you’re advised to apply a registry fix, as explained in the KB919521 article.
- Updated the notes for 891122 and 941569. These updates are not only for Windows Media Player 9.
- The Script updates 971961 and 981350 are not only for Script 5.6, but for 5.1 too (thanks tomasz86).
- Updated the folder for scripten.exe (Windows Script 5.7) from HFSVCPACK_SW1 to HF (thanks My2GirlsDad and tomasz86).
- Updated the notes for MDAC in the Select the Correct Version part of the Updates page. There are problems when slipstreaming both MDAC 2.53 and 2.8 together (thanks tomasz86).
- Updated the notes for 899456 - MDAC 2.81 installer (thanks mikesw and tomasz86).
Superseded updates
- 979402 is superseded by 2378111 (Windows Media Player 9)
- 935839 is superseded by 935839-v5a.
- 975542 and 981349 are superseded by 2510581.
- 980195 is superseded by 2562937.
- 324178 is superseded by 975558.
Removed
- Removed 2443685 (replaced by 2570791).
- Removed Adobe Flash Player SWFLASH.CAB, 29 June 2011 release (10.3.181.34).
- Removed 917344 (replaced by 971961).
- The previous broken version of 2416400 (replaced by 2416400 v2).
For all changes, please read the Changelog.
0 -
WINDOWS2000-KB838969-X86-ENU.EXE
I quckly checked your list of updates and I can say for sure that this one is obsolete.
That one is replaced by 961063 - Dns.exe 5.0.2195.7260.
0 -
0
PE Tool for creating patches
in Windows 2000/2003/NT4
Posted
Hi WildBill,
After installing the update, I get this error on reboot (the progress bar on the Windows 2000 boot screen having reached 100%):