
LLXX
BannedContent Type
Profiles
Forums
Events
Everything posted by LLXX
-
TFTP? Here's one: http://www.winagents.com/en/products/tftp-client/index.php 81Kb, not bad... but could definitely be made smaller.
-
Enable48BitLBA | Break the 137Gb barrier!
LLXX replied to LLXX's topic in Windows 9x Member Projects
That was my original goal, but it's a bit too much, and I couldn't figure out how to assemble the driver correctly. M$'s is already written in Asm, and although not maximally optimised, it's quite a bit better than some of the other drivers they've written... -
Sun Java and Flash Player Don't Mix
LLXX replied to bearsowner's topic in Windows 9x Member Projects
That vulnerability should hardly be of any concern, as noone should be allowing arbitary sites to use ActiveX. You can get 8.0.33.0 from the Flash Player 8 Update located here: http://www.adobe.com/support/flashplayer/downloads.html#FP8 (comes with the standalone players and a lot of the other players too, that's why it's so large) BTW, here are some older versions: http://www.adobe.com/cfusion/knowledgebase...cfm?id=tn_14266 -
Run MemTest86+ for a few hours.
-
Even the illegal copies still run, just the message about "Windows is Not Genuine" appears.
-
Well, been there, done that, doesn't work. I tried every version of chkdsk that can be run and even scheduled a bootup run to get no windows interferance. No luck. Though I can happily state that Norton Disk Doctor does indeed find an error on the drive and suggests that I run chkdsk to fix the problem. yay! Read before posting... The NTFS file system does get corrupted in strange ways... might be time for a complete backup, reformat, and restore.
-
Why don't you just download it from M$... it's free. BTW, if the only thing you're anticipating about Vista is its sounds... I don't think that's much of a reason for wanting it
-
LCDs either don't display anything at all on the older models, or a message similar to "Signal out of range" if run outside of spec.85Hz refresh isn't supported by many monitors, it's best to use ~70 or even 60Hz when switching between monitors (the flickering is bad, but better than seeing nothing or a scrambled image.)
-
Sun Java and Flash Player Don't Mix
LLXX replied to bearsowner's topic in Windows 9x Member Projects
Flash is actually one of the easiest components to remove/install/enable/disable. All you need is the OCX (swflash.ocx or flash8/9.ocx, depending on the version) and put it somewhere, then (un)register it with regsvr32.Hint for finding older versions - Google for the filename and look around. I can help you find older versions if you want. -
Those files just look like they're for power management features, and the INF just sets maximum resolution and specs. Totally unnecessary.I have several video cables, where I cut the DDC lines to prevent it from "detecting" the monitor, so Windows just shows a Standard Monitor device. Show me an example of a monitor that *requires* a separate driver (and NOT a video-card driver) and I may change my opinion. As is, I should just expect to plug any monitor into my machine and, as long as I set the video card's refresh rate and resolution within its specs, it should work perfectly fine (maybe with some adjustments needed, such as the Image Lock I mentioned earlier on LCDs). So far my experience has agreed with this. ... drivers *are* needed for the keyboard (i8042-something under 9x) and mouse (mouse.drv). Speakers and microphones... sound card drivers would handle those.
-
No, nor do I intend to. Mine works, that's good enough. No, I'm not putting them back, I had enough trouble trying to fit the high-sector-count initialisation code in that tiny space. Any HDDs old enough to require the delay would presumably be less than 128Gb anyway, and if data corruption is noticed, original ESDI_506.PDR should be used.Should've revived the Enable48BitLBA thread for that... stop going off-topic
-
Possible to upgrade the BIOS with such support?
-
Fixed. There probably will be another project similar to nLite... I wonder how slimmed-down Vista can be made.
-
ROFL... EXEs are a PC executable format. Mac has its own format which is completely incompatible.
-
Not too sure but this might be the 2Gb limit... that's certainly quite an old machine.
-
You wouldn't happen to have an MD5 of that .exe, would you? I found a copy, but I don't trust where I found it from... 917d52668d08b8d305d40404698b6bd1 size 14032 bytes
-
Since when were monitors "XP compatible" only? As in, it won't even work under plain DOS? The "blurring" symptom described in that link is common on LCDs connected via 15-pin analog interface, and is caused by misaligned signals (the interval for each pixel is not centered exactly within the sampling interval of the input driver, so in effect the analog signal is overlapping pixel boundaries). All LCDs with an analog input have an Image Lock or Image Phase or similar adjustment for aligning the signal properly. Also note that a bad cable can have the same effect, and some video cards don't have very stable dot clock oscillators, but the effect is much less obvious with a CRT since they don't have distinct pixels unlike LCDs.
-
Run CHKDSK on the drive, this is a common problem of a bad shutdown and is called lost clusters/incorrect freespace count.
-
[quote name='XtremeMaC' post='152152' date='Jul 16 2004, 07:59 AM']well easiest u can do is to disable theme support from services.msc or u can go to display properties and choose windows classic.[/quote]More clearly, enable themes and use the default skinned theme, then stop the theme service.
-
Do be aware that if they're determined enough, even DeepFreeze and a passworded BIOS isn't going to stop them from doing what they want. I've done this several times with public computers... usually clearing the BIOS password or using one of the well-known master passwords to get it to boot from my USB drive so I can use my own environment.
-
If you delete NTLDR it'll actually say "NTLDR is missing." (Try it sometime, just remember the fixboot command from recovery console...)The "DISK BOOT FAILURE" looks more like a hardware error.
-
What size is it, and how old is the BIOS? It might be a disk capacity limit in some older BIOSes.