hello every one ..

iam having a problem with a cisco packet tracer 5.3

while i was working in a lap after i saved my configuration then it wont open it again when i tried to open it
a message said this file is not compatible with this version of packet tracer also i have tried to open other laps same message appear
i didnt know whats the problem ?
any help please .

yea. the thing about PT is it is still (after many versions) very unstable. I run into issues all the time. my configurations are solid however they dont work.
when I open a new file and do it again it works.

PT is fuggy as buck my friend.
best to combine PT with real gear. a lot of people may disagree but for lab purposes really nothing beats a live lab.
GNS3 is also good however it too has its bugs as well.

obviously having a lab with live gear may not be an option as is can be very costly. there 3rd party resellers you can buy gear from but that still can be expensive. I dont suggest ebay. its really hit and miss.

if you are a hard core cisco guy and really want to invest, I propose dropping 1,000 on some gear.
you can actually get a fair amount of kit for that if you know where to look.
make sure you get the right gear too. I'd search this forum for posts on CCNA,NP and IE lab setups.


hope this helps!

_________________
CCNA, CCDA, CCNA-SECURITY

Rubbish! Interesting how it's always the software or hardware! I've run all versions of PT on XP, Vista and Win7 and the only real sofware bug Iever encountered was a multi-user issue that was later fixed.

If your configurations really are "solid" and supported by PT they will work.

Aubrey

_________________
The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn. Alvin Toffler, "Future Shock" 1970

i got caught out with the pt bug that wiped my entire case study that i was working on. thank god for backups

What bug was that? Did you report it? There is a mechanism to do that and the PT dev team are always keen to fix it. Just because software doesn't do what you expect at that time isn't necessarily a "bug".

I might seem to come on quite strong on this but I encounter daily students who blame the software, Windows, the IOS and hardware for problems caused by their misconfiguration and ignorance. Two nights ago a senior evening student (working in the industry) and getting ready for his CCNA was adament that I swap out a WIC-2T card because the serial interfaces on his routers were flapping when he was trying to configure PPP. After 15 minutes of "suggesting" that he check his configs very *carefully* I finally had to say 'have you put a clock rate on the DCE interface?' Response - a very quiet "oh".

In terms of PT, 3 or 4 years ago there was a outcry from some students because a PT "bug" caused display problems with a particular ATI video card. Turns out it was a card/driver fault - heavy CAD programs such as AutoCAD , Microstation and Protel/Altium also had the same problem!

So don't jump to judge is all I'm saying

Aubrey

_________________
The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn. Alvin Toffler, "Future Shock" 1970