| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 68751 | 2006-05-09 22:41:00 | Big troubles with downloads. | JJJJJ (528) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 453596 | 2006-05-12 03:46:00 | SolMeister, are you saying that the NV firewall is not a firewall? A firewall is software (which, of course, runs on hardware) which examines data packets moving between a computer and a network. It might stop packets, if the rules don't allow them. But it mustn't, can't, ever, change the data. If the data are allowed, its packets are transmitted. A firewall's not a filter. It's a gatekeeper. Jack tried to decompress a known good file from a CD. That will have involved reading from the CD into a memory buffer. That happened without errors ... CDs have a lot of error checking. But the decompressor said the file was corrupted. So "NV non-firewall" intercepts data on its way from memory to the CPU? And changes it? How? (and why?) Where data go in memory depends on what has been loaded previously. After a format/reinstall of Windows, Jack's system will have a different memory map unless he installed applications in exactly the same order, with the same options. I doubt that. ;) Often bad memory goes undetected until an application which does extensive checking uses the bad locations, or executable code uses them. A word processor can have data errors without problems. You know you can't spell, so a few wrong characters don't worry you. A decompressor requires perfect files. It notices. That's why loading OSs is a good test for memory -- huge compressed files. But Jack has 1GB or so. Even loading XP might not use it all. But Jack is happy again and can crash his jumbo jets much faster. ;) |
Graham L (2) | ||
| 453597 | 2006-05-12 04:16:00 | The NV Firewall "should" only affect the NV Ethernet traffic but the firewall, drive controller and NV Ethernet hardware are all in the same chipset. Who knows what interactions occur. NV have been famous in the past for MB IDE controller software that caused corruption. | PaulD (232) | ||
| 453598 | 2006-05-12 04:45:00 | Graham: In the past you have mentioned that installing Windows was a good test for showing up faulty RAM but Jack managed to format and reinstall Windows with no problems . It's not clear, however, whether he used the new PC's RAM or the RAM from his old PC but he does say that the latter had the same problems unzipping files so how can it have been the RAM? It wasn't just the 1GB file that Jack could not decompress, a 100MB file would not unzip either . Are the cows nearly home yet? :p |
FoxyMX (5) | ||
| 453599 | 2006-05-12 05:17:00 | . . . But Jack has 1GB or so . Even loading XP might not use it all . . . . XP has to be installable on machines with a lot less than 1GB . The installer's not designed to test all memory; that just happens as a bonus if you've got 128 or 256 . The file he had previously downloaded on the old machine could be decompressed on that machine . He copied it to a CD and it wouldn't work on the new machine . We're told now that he moved the memory at some stage . I can only go by what I know at the time . My ESP does not include precognition . A sad deficiency, I know . :blush: A firewall which modified packets would be an evil thing; a "firewall" which actually goes further and modifies data during processing might be very clever, and a further step towards the totally non-deterministic computer, but hardly useful . :badpc: |
Graham L (2) | ||
| 453600 | 2006-05-12 08:21:00 | Just as a point of interest I have 2 gigs of ram. and an Athlon 64 x 2 4200 cpu. | JJJJJ (528) | ||
| 453601 | 2006-05-13 04:37:00 | Stop skiting. :D I bet you can't type any faster with it. | Graham L (2) | ||
| 453602 | 2006-05-13 04:52:00 | Stop skiting. :D I bet you can't type any faster with it. Can't spell any better either. |
JJJJJ (528) | ||
| 1 2 3 4 | |||||