Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by James_A

  1. Thanks for the reply. I wasn't asking that all lines be wrapped, because I fully understand that the purpose of the CODEBOX is to not introduce linebreaks. For very long lines, however, the CODEBOX introduces a horizontal scrollbar as well as a vertical scrollbar (as can be seen in the post I quoted, above). It's just that the board software doesn't add this horizontal scrollbar until the CODEBOX is something like 1600 pixels wide. Since this changes the width of the whole post, it makes the whole post difficult to read, on laptops or anything else with a non-widescreen monitor. For me, a scrollbar appearing after about 800-1000 pixels would be much nicer. I'm not saying that this is a bug, just that it's an inconvenience or a little awkward. Anyway, it seems from your reply that I'm asking for a feature request in the next version of IP.Board rather that a quick-fix to the BBCode. It looks like this is a change to the .php code itself. So thanks for following this up. .
  2. Thanks for the explanation, Eldmannen. My mistake was to read \w as an actual "w" and not as [A-Za-z0-9_]. So I was reading it as "zero or more of w" which is obviously wrong. Correcting the auto-correction on the board helps as well! .
  3. This question is prompted by the following post: https://forums.lunarsoft.net/index.php?s=&showtopic=2807&view=findpost&p=21465 Is there any way that the Code box can be made narrower before the horizontal scrollbar kicks in? I found the above post quite difficult to read on the 1024 wide (laptop) and 1280 wide (non-widescreen desktop) monitors I use around here, because the whole post (not just the Code box) expands way past my screen edges. -
  4. Neat! Microsoft KB articles (KB836961 for example) generally recommend the following URLs to be put in the Trusted Zone in order to access WU: I'm not very good with Regular Expressions, but I'm trying to match update.microsoft.com/windowsupdate against: (host.match(/^(\w*\.)*microsoft\.(com|org)$/)) I understand the start-of-line & end-of-line parts OK, but I'm a bit lost in the middle. Also, is that a typo at the end of: (host.match(/^(\w*\.)*getfirefox\.coMS/)) Apologies if it is not, but what does it mean? You might also want to match www.mozilla-europe.org which is used round here (it downloads from download.mozilla.org though). Once the shortcuts are removed from the Desktop and Quick Launch bar, this PAC file should make it quite difficult to use IE instead of FF. Thanks for filling-out the idea. -
  5. Interesting. I was thinking about the good and bad points of each. May I ask why you prefer c't Offline Update?
  6. Reformatting your PC won't fix it, because it's not a disk issue. Referring to the OP (Post #1) a CPUID of 0673 means a Pentuim III between 450 and 600 MHz in a SECC2 (meanin a slot) package. The correct Vcore for 4 of these is actually 2.0 volts (as shown in the POST) apart from two (533B and 600B) which take 2.05 volts. Either the Power Supply is starting to fail, or as DJLizard says, it means nothing.
  7. Yes! The idea of using a PAC file to block stuff from the internet was conceived about 12 years ago by John R. Lo?Verso (http://www.schooner.com/~loverso/) who used it to block adverts. It is far superior to using the HOSTS file for this purpose, because it is much quicker. A good article on the subject was written by Sheryl Canter about 4 years ago for both O'Reilly and the American version of PC Magazine. There's a copy of the article on her web-site (Kill Internet Ads with HOSTS and PAC Files). It seems to me that what you need is an extreme version of this technique, which only allows the Windows Update URLs and blocks everything else. The BlackHoleProxy Utility mentioned in Sheryl Canter's article does not seem to be available any more, but this should not matter to Internet Explorer. --
  8. You can probably do this by using a PAC file. Whitelist the Microsoft URLs associated with WU/MU and send everthing else to localhost or a black-hole proxy. --
  9. No need to fall back to SDN, Update 10 is at Java.com as well.
  10. Not quite! Critical updates are selected automatically for you.
  11. Well, that seals its fate as far as I'm concerned. That's far too invasive for me! Thanks.
  12. You say, of nLite: Does that still hold true, two years later? If so, that is enough to put me off, whatever other merits nLite may have.
  • Create New...