What a wonderfull world

Mike in Colombia!

2006-09-10T06:38:00.000-07:00

Mike in Colombia!

that is a nice story...

Hide files in MS Windows( exploit the bug in rename operation)

2006-07-18T20:47:00.000-07:00

(click the image for large size)

We all know the file path length has some limit.

Now if you creat a deep "folder" tree then at some point you will not be able to create any more folders.

Suppose we have such a folder tree.
We can build the tree using this batch file.
----------------- (Cut and paste this in a text file and rename it foobar.bat file)
mkdir deep_tree
copy foobar.bat deep_tree
cd deep_tree
foobar.bat
------------------------

Run the batch file and stop it when you get the message "The filename or extension is too long"

Now traverse the created tree..say go some 6 levels deep.
Now rename the folder deep_tree to a very long name such that the path length to some lower level tree exceeds the path length limit.( We can do this because the rename operation doesnot check this.)

The end result is : the lower level folder becomes un-accessible .

In fact,You cannot go into it by navigating through mouse.
Also,You can not delete/cut it/copy it
Also,You cannot search its contents.
Also,The size of its contents will not come in the size of any of its ancestors.

Software Design/Development Process for final year projects

2006-07-17T00:02:00.000-07:00

I had a rather fine experience during my final year project.
And I will like to share it.

My final year project was development of a client and server software for FTP.

I follwed these steps strictly :
a) Read the specifications . In my case these were the relevant RFCs.In other cases, students might be given some specification or may have to prepare one. But reading the whole specification is a must.Since we are not working in a commercial setting,I think it is possible to freeze the requirement specification.

b) After doing step a), u must've got an idea about the data/inforamtion that ur software would be handling.You must be knowing about data flow diagrams.(Read wikipedia or google....hey u always have ur library ..go there). Making a data flow diagram gives you more understanding about the software.It also makes you realise how much u exactly understand the specifications.Believe me DFD( Data Flow Diagrams) really help.

c) Based upon Data Flow Diagram , u can divide ur software in sub- modules. Descide the interface between the sub-modules and the between the system and external environment(human users , other apps/spftwares ).

d) Now is the time to deside the data structures --which will represent the info flowing through the sub-modules and the interface i.e. interaction functions between sub-modules.

c) Now u can start the coding

This was all I could recall. But one thing is certain, I was successfull in completing my project by following above process.

I will elaborate more on each step in future posts.

Step a) took 1 month . This covers Software Analysis.
Step b), c) and d) took about two weeks. This is Software Design.
Step e) took (believe it or not )just 7 days. This is Implementation and Testing .

So u get the point, the most important step is analysis (reading the specs) and design.if these two have been done properly, coding can be done very fast.

Please leave comments or mail me at aman_buckup@gmail.com

Hello World :

2006-07-16T01:32:00.000-07:00

This is my first post. And I have only one thing to say. The world is beautifull.You are wonderfull.I am wonderfull. Keep smiling.