Is it advisable to use this motor with A4988 and or DRV8825 drivers. Which shows current rating as 1.7A.
Should be fine. Datasheet on them can be found here: http://www.longs-motor.com/productinfo/detail_12_25_112.aspx
Confirm same model used on my old makibox 
That is a very low-resistance and low-inductance motor. DO NOT use those motors with Pololu 8825s in the default “mixed decay” mode: you will get ripples in your prints at very low motion speeds (such as when rounding curves). My simulator says 12v PSU will have moderate rippling, and 24v will have very severe ripping.
I see this all the time in people’s print photos with 8825s… it’s a very common print flaw caused by printer designers not doing enough drivetrain engineering. They work great for some motors, so people still promote them, but they seriously suck for very low-inductance motors.
You can do some soldering to switch the 8825s to “fast decay” mode and eliminate the rippling. But then they will probably make annoying hissing noises.
The 4988 will perform better than the 8825 with this motor, but seriously, the THB6128 driver chip (eg RAPS128 or SD6128 from Panucatt) is the superior choice for motors with very low inductance. They’re really kick-ass drivers. Great current control due to some clever chopper algorithms, very quiet, works up to about 2A, and has up to 1/128 microstepping if your controller can handle it. (I recommend 1/16 for 8bit or 1/64 for 32bit personally, but it depends on what kind of other load you’re putting on the processor.)
Alternatively, find a motor with higher resistance and inductance and both the 8825 and 4988 will work fine.
Feel free to plug the motor specs into the stepper driver simulator to see for yourself: https://github.com/rcarlyle/StepperSim
(Note that high speed simulation requires knowing the back-emf, which is a multimeter measurement while spinning the motor shaft at a known RPM, but the low-speed rippling that 8825s often have doesn’t require knowing back-emf so you can just plug in datasheet values.)
@Ross_Bagley @Ryan_Carlyle @ThantiK Thanks for your information.