Content Type
Profiles
Forums
Events
Everything posted by jaclaz
-
It starts to look every day more like an Ed Bott vs. Gordon Kelly war. jaclaz
-
Another reason why the IoT may not be that good an idea ...
jaclaz replied to jaclaz's topic in Technology News
VTECH has found a neat solution to security: http://www.troyhunt.com/2016/02/no-vtech-cannot-simply-absolve-itself.html changing the Limitation of liability in there T&C (Terms and Conditions) to include: jaclaz -
Yep, and it is a different level of "priority". Like: 1. my computer doesn't boot, HELP! <-code RED ... .... .... .... 2387. I cannot see a cute lolcat or latest prank video, HELP! <- code "whatever shade of pale white doesn't really matter" jaclaz
-
Maybe people are starting to see tablets for what they are, a VERY LARGE smartphone (which in itself is not a bad idea IMHO) and not for what they attempted to market them (a very small PC replacement) . jaclaz
-
Another reason why the IoT may not be that good an idea ...
jaclaz replied to jaclaz's topic in Technology News
Well, it's OFFICIAL now: http://www.theguardian.com/technology/2016/feb/09/internet-of-things-smart-home-devices-government-surveillance-james-clapper jaclaz -
Like this one? jaclaz
-
Sure they do , they have the secret seven, remember : http://homepage.ntlworld.com./jonathan.deboynepollard/Humour/microsoft-monopoly.html jaclaz
-
Well , the point as often happens is not about why it was designed, but rather about how it was implemented. Surely, when it works, it works very nicely. jaclaz P.S.: you may well write the rules of the SATA club the way you want, but you simply cannot state that the rules for the IDE club that I just invented are not true, you are not even a member whilst I am a founder!
-
Just in case, the first rule of the IDE club is: 1. You don't use Cable Select jaclaz
-
No ideas, as said earlier there are reports of (partial) success (i.e. Windows 98 installed and then issues with some devices or drivers) but with setup /p i seemingly it installed: http://en.community.dell.com/support-forums/software-os/f/3524/t/3016125 jaclaz
-
180x120 AND oeminfo.ini http://www.trishtech.com/2010/02/change-oem-logo-in-windows-xp/ jaclaz
-
I am not a subscriber as well but I can access it. Maybe it depends from the browser or your location. You may want to copy the link, paste it in a new browser window and then re-paste it and reload the page, my good ol' Opera has issues with the site but Chrome based browsers should work (just checked with Iron). jaclaz
-
It is free once you will have paid money to subscribe, check again the posted scheme, step #1 requires that you pay money. jaclaz
-
Maybe you could make use of DosBox: http://www.dosbox.com/ or vDos: https://www.vdos.info/ Or you could use VirtualBox and: http://virtualboxes.org/images/freedos/ jaclaz
-
Usual steps: 1. Subscribe 2. Download 3. ??? 4. PROFIT!!! jaclaz
-
Sure , that is correct ( in theory), but you never know what actually happens under the hood, just like ACPI, in theory Windows 98 supports it, but in practice it causes issues, possibly in connection with *some* not particularly "friendly" or "well coded" BIOSes (and specifically DELL has a record for modifying or botching BIOSes on their machines) anything (and the contrary of it) may happen, as you can see from the given reference years of hit-and-miss have been accumulated on the board, installing 98 or more mordern hardware is not as easy as it should be, but with some perseverance (and a lot of testing) I am pretty sure it is doable :. jaclaz
-
It is "strange". While you may actually want to have two of Rloew's patches, the SATA one and the RAM one (for actual use of the PC), I have seen reports of people installing on that same machine model without issues, but haven't seen details about whether they were using a SATA or a IDE disk (in theory there should be no problems with a SATA disk if the BIOS is set in in "IDE compatibility mode" or similar, but you never know) You could try (just for the sake of confirming or excluding that the SATA disk is involved) to install the 98 on the 40 Gb IDE disk. If - by any chance - you have )or can borrow) a 512 Mb (or smaller) stick, you could exclude the possibility of "too much RAM" causing the issue. In any case, I would try removing one of the two 1 Gb sticks. Go through (I know it's a lot of info) this: http://www.msfn.org/board/topic/118097-day-to-day-running-win-9xme-with-more-than-1-gib-ram/ Or wait a bit, surely some of the members more "current" with windows 98 installs on "recent" hardware will chime in and assist you. jaclaz
-
...meanwhile in Cupertino ... http://www.theguardian.com/money/2016/feb/05/error-53-apple-iphone-software-update-handset-worthless-third-party-repair A software update that retroactively checks the otherwise and until then prefectly working device hardware and irreversibly bricks it (making you lose ALL your data). Not even the good MS guys have managed (yet ) to do something like this (or maybe they have it on the Lumia's, but that doesn't really count ) jaclaz
-
Make Static Website available to internet
jaclaz replied to urgenthelpneeded's topic in Windows Server
Is this urgent? jaclaz- 14 replies
-
- windows server 2008
- server
-
(and 3 more)
Tagged with:
-
Strangely enough, clonezilla won't actually produce a "clone" image (and "normally" not even ghost), but rather a "backup" image. Depending on which kind of image you want to make you might want to use Partition Saving instead: http://www.partition-saving.com/ See here for a quick examination of the differences between images and imaging apps: http://www.msfn.org/board/topic/157634-hard-disk-cloningimaging-from-inside-windows/?p=1007158 jaclaz
-
@drugwash JFYI (and as an example) what I personally call the "worst BIOS of all", i.e. the "InsydeH2O" BIOS which is actually becoming very common on laptops, in some versions had (some say on purpose "blacklisted", some say "failed to mind their own business" or "whitelisted a few common sequences only") some given sequence in the MBR code (a small change had to be done - twice if I remember correctly - to grub4dos grldr.mbr to have it working). jaclaz
-
Sure SQlite has a CLI version, if this is what you are asking: https://www.sqlite.org/cli.html jaclaz
-
Not really-really. ONLY Windows NT based systems are seemingly "affected" by the device "Removable bit" (if this is what you are refeerring to, but if it is then it can be flipped on and off at will, once you get the "right" tool AND you manage to use it ). It is much more likely that the "Pendrive" has been "normally" formatted under a NT based system (and since it is "Removable" under this OS it has been NOT partitioned). BIOS's want partitioned devices and don't like "superfloppies" (and don't care about the "Removable bit"). Quick blast to the past : http://jaclaz.altervista.org/Projects/USB/USBstick.html (only to show how fast ten years pass by ) @Kizoky How (exactly) was the pendrive partitioned? Which OS does your "other" computer run? If any of the NT family use a suitable tool to partition and format the (removable) pendrive, such as the original HP tool, or this (fuwi's tool): http://www.911cd.net/forums//index.php?showtopic=21702 or RMPREPUSB: http://www.rmprepusb.com/ jaclaz
-
And now, for no apparent reason, a link to Donkey's Stable , do check the WinExplorer there: http://www.donkeysstable.com/ http://www.donkeysstable.com/winexplorer.htm @drugwash Why, in my day, all we had was a Z80 with 1 (one) Kb of RAM, had to actually solder the board .... https://tinyapps.org/blog/misc/200702250700_why_in_my_day.html .... and we LIKED it! jaclaz
-
Not really "always", many times this is not voluntary, simply the new version of the MS compilers changes default, Author does not check it and the result of re-compiling is a compiled executable that is "artificially" limited to newer OS's. A different case is when the Author uses an API call that does not exist on a "previous" OS (though not really my field of experience, I believe that - with some exceptions of course - there is often a way - IF the Author is willing to take the extra time - to avoid the new API call). In this latter case the executable is actually "incompatible" unless it is re-compiled with the needed replacement/workarounds. jaclaz