Jump to content
SAU Community

Recommended Posts

is this a typo that ms word spell check missed?

The reason I am a fitter welder and not an IT pro is I couldn't put up with end users (uneducatable stupid endemic retarted skatterbrains) and I make more Money (tried to hire a tradesman lately?)

Anb no i can't spel but htis site heelps http://thesaurus.reference.com/

How could MS get through a firewall? mmmm let me see well first u use ur puter dont u? Ah u do don't u! so u use software 2 visit certain sites that when u get there u stay at 4 a while then move on. While on this site u dload and upload bits of info (its the only way a packet sending network works) what sort of info do think the site wants and remember this info is on every packet u send

first network type next (important one this one) OS type

now if MS has an alert on this feedback and (its allready through your firewall by use of the same dll that ie uses) it matches your id with reg id its all embedded in the software

This is my theory and nobody is allowed to use this theory:mad:

  • Replies 93
  • Created
  • Last Reply

Top Posters In This Topic

How could MS get through a firewall? mmmm let me see well first u use ur puter dont u? Ah u do don't u! so u use software 2 visit certain sites that when u get there u stay at 4 a while then move on. While on this site u dload and upload bits of info (its the only way a packet sending network works) what sort of info do think the site wants and remember this info is on every packet u send first network type next (important one this one) OS type now if MS has an alert on this feedback and (its allready through your firewall by use of the same dll that ie uses) it matches your id with reg id its all embedded in the software

That's a fail Terry... Do not pass go, do not collect $200...

Back to school you go...

hahah

this thread is funny

so many conspiracies ... so little time

and for the record

IT Masters Degree , A+, N+, MCP, MCSE, MCSA, CCNA qualifications and I currently work for a "Microsoft Premium Partner" development company and Terry is speaking a lot of shit

Wow, its true.. They really do give out MCSE qualifications to anyone!

Cheers for being a living, breathing proof of concept for my theory "MCSE requires no sk1llz". Now I have a link to send anyone who disagrees:

http://www.skylinesaustralia.com/forums/me...hp?userid=17300

And I have a link to a know his own name super geek

http://www.skylinesaustralia.com/forums/me....php?userid=627

any qusetions about this thread should be directed to the higher power listed above

And I have a link to a know his own name super geek

http://www.skylinesaustralia.com/forums/me....php?userid=627

any qusetions about this thread should be directed to the higher power listed above

Have you considered one of these?

http://www.tafe.qld.gov.au/courses/literac...eracy/anlc.html

Might be a good qualification to add to your MCP...

Some members here are probably wondering how I could sprout such rubbish and be believable, I'll tell you a story and make up your own minds.

This mate of mine bought a computer in 1987 and with it came DOS 5 and if you know anything about d5 you'll know that it doesnt do much except run your computer. So he had to buy software to do anything with it, now not being of the overly funded type he asked around and people "loaned" their software to him and since that day till 2004 he found ways to never pay for software, he even learnt how to crack games and such, in all this time he upgraded his own computer to run about a year behind the current "best" and had 4 computer game net setup at home in 1997 all on loaned software and connected by gateway to intenet. In time he learnt that some people dont like ppl who do this and had to fortify and so the story goes.

Along comes XP uses that for about 3 mths and thinks one day this needs updating, so update he does and lo and behold he starts having unexpected shutdowns when online, only online so he reformats, reloads no good. this has all been behind a firewall on same computer so he setup a dedidcated firewall and runs through that to internet still the same. Gives up and buys xp on harddrive for half hardlynormal at the disc shop, a sad day for him as it marks the end of a golden era.

Oh and the firewall thread i posted was utter rubbish it "may" have worked in the early days but with the strong encryptions of today it cant happen, just thought I'd see where it led.

There has been many MS updates which makes a system unstable, so this is proof of nothing. Often XP ( Crap IMO) offers you a driver update which is unsuitable and forks things, seen it on several friends' PC's, a rollback of driver fixes this. As for Windows update, well if you go there with a blacklisted serial your not to smart to start with.

:D

So your "friend" has a dodgy version of windows which he updates from the MS site after which it then starts to crash as soon as a particular service starts and runs when he is connected to the internet.

Therfore ergo that translates as someone at the evil Microsoft corporation monitoring when certain systems come online then logging in with their secret MS login that passes through external hardware firewalls and crashing the system.

Or alternatively, as Merlin said, it could be that an update has a problem with one of the service's that runs whilst on this particular hardware setup when on the net, which is consequently fixed by a later update which the dodgy version can't download as it is one of the updates that are not available for blacklisted serials.

Hmmm which is more likely...

Occums Razor or the Principle of Parsimony my friend

Pluralitas non est ponenda sine neccesitate

(plurality should not be posited without necessity)

Agree with what Merlin has mentioned...

modr33s2, As to your friend's system keeps shutting down after going online has he checked his event logs for any weird rpc errors? What I am referring to is blaster worm or a variant of it. You friend's problem sounded very must the syntoms of a blaster worm/variant. Firewall or IDS would not help in anyway at all as the worm is attacking your friend machine's rpc service locally.

Nothing is impossible these days when it comes to security, regardless of how strong of an encryption is used. As encrytion is being cracked everyday it is the reason why there is a constant drive in developing stronger encrytion. The safest system is one that is physically secure ( in a bomb shelter or something) with nothing but a keyboard, mouse, monitor and the box connected.

For a normal computer user online, a firewall and anti virus software is just the basics that everyone should have. You would be silly not to at least have these two if your on the internet and of course you have to ensure that they are setup appropriately at the start and also is constantly updated.

The comment of linux is more secure than windows xp or the other way around is rubbish. How secure the machine is depends on how much time the person using the machine take initially to setup and perform the daily task of checking the system. Linux used to be by default more secure as one of its versions was the first to integrate firewall install and easy setup as part of its install. XP did not offer integrated firewall until service pack 2 was released and also at the same time Windows software is more globally used and hence is more targetted for attack.

Just thought I'd add in my 2c worth. :D

What did the error logs say when the system crashed? .... I know you being a MCP and a "mate" you would have checked these for "him".

Or did the error logs not eventuate because the Evil MS monitorguy wiped the logs after he crashed the system with his secret MS login so as to cover any traces ... or replace the real error logs with some fake ones to look like it was something else other than the intrusion of privacy that it really was?

your conspiracy theory is a great story though :D

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...