I'Ve Never Put More Than 13 Gallons In...
Last time I left the gas light on for a while I went for 35 miles before filling up, and still only put about 13 gallons in (exact amount escapes me.) I usually go about 20 miles after the light and have to put in less than 12. I get 30 - 35 mpg (mostly highway), so if the tank is 15 gallons (according to the manual) I would theoretically have over 100 miles after the light comes on. Not sure if you can actually run the tank down to the very last drop, and not really eager to test the theory.
Story replies
Like all new cars, the Mazda3 includes a 'reserve' tank. More or less, once the tank dips below a certian level for a predetermined amount of time, you run out of gas. Truth be told there is still alot of gas in there, if you have evere needed to remove or replace a gas take you know what I mean. Each vehicle has a different procedure for acsessing this extra fuel. It may be as simple as turning the car off, then starting it agian, in others it's more complex involing a rather langthy procedure involving locking, unlocking, starting, buckling, and unbuckling. Other times it's a button or switch. Take some time to read you manual and talk to service personel at the dealership to figure out what it is for your car.
If you have to unlock it, then the extra fuel is not very useful when you are out of gas. Shouldn't it be automatically accessible when the car is out of gas?
Hi,Very good program, tkhnas for it. I have some recommendations:- An "execution delay" parameter to run the executable program when a change is detected. For example, run the application 5 minutes after the change has happened- Collect the change events during the "execution delay" and only run the application once.The above is for the purpose below:- I run unison to sync folders, unison takes some time to sync.- I don't need unison to run each time since there can be multiple changes in a minute, for example, deleting many files and directories, moving files from here to there, which can create multiple event.- If I could delay the run for a configurable time (ie 2 minutes) and if we run the unison only once during this 2 minutes (in case any change happen), it would be perfect.- In the current configuration, each time a change happens, a process runs, which is a bit overkill for my purpose.It would also be good if the batch file or executable window can be hidden from view, not good to see something popping up each time I make a change. It shall be transparent. If I wonder, I can check the log file.Many tkhnas again!
Hi,Very good program, tkhnas for it. I have some recommendations:- An "execution delay" parameter to run the executable program when a change is detected. For example, run the application 5 minutes after the change has happened- Collect the change events during the "execution delay" and only run the application once.The above is for the purpose below:- I run unison to sync folders, unison takes some time to sync.- I don't need unison to run each time since there can be multiple changes in a minute, for example, deleting many files and directories, moving files from here to there, which can create multiple event.- If I could delay the run for a configurable time (ie 2 minutes) and if we run the unison only once during this 2 minutes (in case any change happen), it would be perfect.- In the current configuration, each time a change happens, a process runs, which is a bit overkill for my purpose.It would also be good if the batch file or executable window can be hidden from view, not good to see something popping up each time I make a change. It shall be transparent. If I wonder, I can check the log file.Many tkhnas again!
Hi,Very good program, tkhnas for it. I have some recommendations:- An "execution delay" parameter to run the executable program when a change is detected. For example, run the application 5 minutes after the change has happened- Collect the change events during the "execution delay" and only run the application once.The above is for the purpose below:- I run unison to sync folders, unison takes some time to sync.- I don't need unison to run each time since there can be multiple changes in a minute, for example, deleting many files and directories, moving files from here to there, which can create multiple event.- If I could delay the run for a configurable time (ie 2 minutes) and if we run the unison only once during this 2 minutes (in case any change happen), it would be perfect.- In the current configuration, each time a change happens, a process runs, which is a bit overkill for my purpose.It would also be good if the batch file or executable window can be hidden from view, not good to see something popping up each time I make a change. It shall be transparent. If I wonder, I can check the log file.Many tkhnas again!